@joshcooper we had originally talked about __not__ surfacing Windows default service user / group, but as it turns out -- I think this is the right thing to do.

I think top-level default config is the right place to do this, and then this also provides a point for users to configure these settings if they wish (though defaults should be fine I think).

By not specifying this here, about 15 or so tests do break (on Windows only) that are verifying how the `FileSetting::Service` class behaves.

Note that these same values show up in `service_owner_fallback` and `service_group_fallback` to be more inline with how other operating systems handle this.