Clean up config logging

[seanbudd]

Link to issue number:

None

Summary of the issue:

• Config files would get logged at info level if they were invalid.
• Converting loglevel name strings to integers via getLevelName is deprecated

Description of user facing changes:

Description of developer facing changes:

Description of development approach:

Testing strategy:

Known issues with pull request:

• log.debug will never get logged during initialization, meaning there is no easy way to decide whether or not to log config when it fails to load.

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

[seanbudd]

note this will never log at debug level on systems, as setting the log level from config hasn't happened yet, so the python default level (info) is being used.
We should avoid logging config by default, but that doesn't give good debug steps. Instead should we create a back up?

[seanbudd]

Blocking on the more useful #19966 while we decide what the behaviour should be here