[CHORE] Update logging for automation_library MessageLog changes.

[Sj-Si]

Brief

This PR updates all logging to use the updated MessageLog functions in the automation_library.

This PR depends on Sj-Si:chore/message-log

Changes

The biggest change in this PR is in the Game object, where we removed the printToLog function. This forced all references to game.printToLog() to instead use the MessageLog logging functions.

This helps to decouple logging functionality so that individual components do not rely as much on having a reference to a Game object stored at runtime.

Please review the associated PR linked above for more detailed information on the changes to MessageLog.

Notes

I have not been able to perform a live test of these changes since I don't know how to run the app while using a different branch of the automation_library.

[Sj-Si]

Performed self review of changes. Fixed any issues that I found along the way.

[steve1316]

I will hold off on this until the next version is ready to be released. Just in case we need to refactor the project to use the log level wrappers again.

[steve1316]

Alright I am freezing additional changes for v4.0.1. This PR will be for merged for v4.0.2.

[steve1316]

Had to merge master to this branch as there were too many changes made since. I will start refactoring to use the log level wrappers.

[Sj-Si]

Had to merge master to this branch as there were too many changes made since. I will start refactoring to use the log level wrappers.

One thing I noticed is in a few places the base Log library was used for logging instead of MessageLog. I left these alone since I assumed you intentionally used Log instead of the MessageLog in those cases. I figured that the items logged with Log would have been too verbose for the app's log to display or something like that. Am I correct in this assumption, or do we need to update those log statements as well?

[steve1316]

Had to merge master to this branch as there were too many changes made since. I will start refactoring to use the log level wrappers.

One thing I noticed is in a few places the base Log library was used for logging instead of MessageLog. I left these alone since I assumed you intentionally used Log instead of the MessageLog in those cases. I figured that the items logged with Log would have been too verbose for the app's log to display or something like that. Am I correct in this assumption, or do we need to update those log statements as well?

Yup you are correct. Too verbose IIRC.

[Sj-Si]

As for the TAG variable being in all caps, that's just a habit I picked up from some embedded C work I did. I have no clue if that is actually a standard so it's up to you how we handle that. I know android studio gets angry about screaming snake case in some instances so I really don't know how it should be handled.

[steve1316]

Works great in my test runs. LGTM!

[steve1316]

As for the TAG variable being in all caps, that's just a habit I picked up from some embedded C work I did. I have no clue if that is actually a standard so it's up to you how we handle that. I know android studio gets angry about screaming snake case in some instances so I really don't know how it should be handled.

I think I started with all caps for the tag for the aesthetics 4 years ago for some reason haha