Add hosting config support to control 3.x log disablement

[liliankasem]

Issue describing the changes in this PR

resolves #10546

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

• Backporting to the in-proc branch is not required
  • Otherwise: Link to backporting PR
• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)

Additional information

Logs pre-configuration (during host startup) are unrestricted.

Post-configuration, the log prefixes are determined by the following settings:

• DisableHostLogs is true, FeatureFlag is not set, should result in restricted system log category prefixes
  • This is the Default state. This is the only setting that would result in restricted logs.
• DisableHostLogs is true, FeatureFlag is set, should result in unrestricted system log category prefixes
• DisableHostLogs is false, FeatureFlag is not set, should result in unrestricted system log category prefixes
• DisableHostLogs is false, FeatureFlag is set, should result in unrestricted system log category prefixes

[liliankasem]

@fabiocav If I am understanding correctly, your requirements would want this to default to false (0) if not set?

Default behavior: logs ON
Hosting config set: logs OFF
Hosting config set, user feature flag opting out: ON