[#1013] - Enable more granular control over logging behavior

[tw0po1nt]

The Initializer struct now takes a LoggingPolicy parameter, which enables the following options when initializing the SDK:

• default - the SDK will default to using its own internal implementation of the Logger protocol at the debug log level. You can also override the log level by passing your preferred log level in to the enum case.
• custom - the user provides an object conforming to the Logger protocol, allowing for complete customizability of the logging.
• noLogging - the SDK will not log anything

Closes #1013

This code review checklist is intended to serve as a starting point for the author and reviewer, although it may not be appropriate for all types of changes (e.g. fixing a spelling typo in documentation). For more in-depth discussion of how we think about code review, please see Code Review Guidelines.

Author

• [x] Self-review: Did you review your own code in GitHub's web interface? Code often looks different when reviewing the diff in a browser, making it easier to spot potential bugs.
• [x] Automated tests: Did you add appropriate automated tests for any code changes?
• [x] Code coverage: Did you check the code coverage report for the automated tests? While we are not looking for perfect coverage, the tool can point out potential cases that have been missed.
• [x] Documentation: Did you update Docs as appropiate? (E.g README.md, etc.)
• [x] Run the app: Did you run the app and try the changes?
• [ ] Did you provide Screenshots of what the App looks like before and after your changes as part of the description of this PR? (only applicable to UI Changes)
• [x] Rebase and squash: Did you pull in the latest changes from the main branch and squash your commits before assigning a reviewer? Having your code up to date and squashed will make it easier for others to review. Use best judgement when squashing commits, as some changes (such as refactoring) might be easier to review as a separate commit.

Reviewer

• [ ] Checklist review: Did you go through the code with the Code Review Guidelines checklist?
• [ ] Ad hoc review: Did you perform an ad hoc review? In addition to a first pass using the code review guidelines, do a second pass using your best judgement and experience which may identify additional questions or comments. Research shows that code review is most effective when done in multiple passes, where reviewers look for different things through each pass.
• [ ] Automated tests: Did you review the automated tests?
• [ ] Manual tests: Did you review the manual tests?_You will find manual testing guidelines under our manual testing section_
• [ ] How is Code Coverage affected by this PR? _We encourage you to compare coverage befor and after your changes and when possible, leave it in a better place. Learn More..._
• [ ] Documentation: Did you review Docs, README.md, LICENSE.md, and Architecture.md as appropriate?
• [ ] Run the app: Did you run the app and try the changes? While the CI server runs the app to look for build failures or crashes, humans running the app are more likely to notice unexpected log messages, UI inconsistencies, or bad output data.

[Chlup]

I have two small comments otherwise this looks ok.

[tw0po1nt]

@Chlup @LukasKorba Since this is my first PR in this repo, I just have a couple questions.

• Do you guys usually have the PR opener merge, or do you have another maintainer manage that?
• In the contributing docs, it mentions to keep the change log up to date, but it doesn't look like some of the other open PRs have updated that. Would you like me to update that prior to merging this?

[Chlup]

@Chlup @LukasKorba Since this is my first PR in this repo, I just have a couple questions.

• Do you guys usually have the PR opener merge, or do you have another maintainer manage that?
• In the contributing docs, it mentions to keep the change log up to date, but it doesn't look like some of the other open PRs have updated that. Would you like me to update that prior to merging this?

Hi Matthew,

PR opener usually merges the PR after it's approved by some maintainer. Changelog is usually updated for the PRs that change public API. Which this does. Please update CHANGELOG.md file accordingly.

Before merging the PR please make sure that all the targets can be compiled. You can use All scheme for that. And please be sure that tests work. Unfortunately CI currently doesn't run all the tests. Running the DarksideTests can be little challenging. But we can help with that.

Have a nice day. Michal

[Chlup]

I checked the tests and all work fine. Just please fix the compilation of the sample app and you should be good to go.