refactor(logging): separate logging from main

[ReenigneArcher]

Description

In order to properly implement unit testing, main.cpp needs to be split out... so src/main.cpp can be excluded as a source for the test binary. Otherwise when the test is started, it just starts Sunshine, instead of starting the tests.

Also, it will help with the ability to test things currently in main. See https://cuhkszlib-xiaoxing.readthedocs.io/en/latest/external/gtest/googletest/docs/FAQ.html#how-do-i-test-a-file-that-defines-main

This PR pulls logging functions out of main. I started with logging because it is probably the most used out of anything.

In some cases main.h could be removed from the includes if it was only relying on logging. Somehow the code in the new logging.h provides assert and in cases where that became undefined I opted to use <cassert> instead if logging was not needed in that file.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated