[FEATURE REQUEST] MRTKLifecycleManager logging should be optional

[Schroedingers-Cat]

Describe the problem

Whenever we start our MRTK3 based project, we get the following log entries in our Unity console:

[MRTKLifecycleManager] Creating MixedReality.Toolkit.Input.MRTKHandsAggregatorSubsystem
UnityEngine.Debug:Log (object)
MixedReality.Toolkit.Subsystems.MRTKLifecycleManager:Awake () (at ./Library/PackageCache/org.mixedrealitytoolkit.core@e3175375067f/Subsystems/MRTKLifecycleManager.cs:71)

[MRTKLifecycleManager] Creating MixedReality.Toolkit.Input.OpenXRHandsSubsystem
UnityEngine.Debug:Log (object)
MixedReality.Toolkit.Subsystems.MRTKLifecycleManager:Awake () (at ./Library/PackageCache/org.mixedrealitytoolkit.core@e3175375067f/Subsystems/MRTKLifecycleManager.cs:71)

[MRTKLifecycleManager] Creating MixedReality.Toolkit.Input.SyntheticHandsSubsystem
UnityEngine.Debug:Log (object)
MixedReality.Toolkit.Subsystems.MRTKLifecycleManager:Awake () (at ./Library/PackageCache/org.mixedrealitytoolkit.core@e3175375067f/Subsystems/MRTKLifecycleManager.cs:71)

[MRTKLifecycleManager] Starting MixedReality.Toolkit.Input.MRTKHandsAggregatorSubsystem
UnityEngine.Debug:Log (object)
MixedReality.Toolkit.Subsystems.MRTKLifecycleManager:OnEnable () (at ./Library/PackageCache/org.mixedrealitytoolkit.core@e3175375067f/Subsystems/MRTKLifecycleManager.cs:122)

[MRTKLifecycleManager] Starting MixedReality.Toolkit.Input.OpenXRHandsSubsystem
UnityEngine.Debug:Log (object)
MixedReality.Toolkit.Subsystems.MRTKLifecycleManager:OnEnable () (at ./Library/PackageCache/org.mixedrealitytoolkit.core@e3175375067f/Subsystems/MRTKLifecycleManager.cs:122)

[MRTKLifecycleManager] Starting MixedReality.Toolkit.Input.SyntheticHandsSubsystem
UnityEngine.Debug:Log (object)
MixedReality.Toolkit.Subsystems.MRTKLifecycleManager:OnEnable () (at ./Library/PackageCache/org.mixedrealitytoolkit.core@e3175375067f/Subsystems/MRTKLifecycleManager.cs:122)

These messages are not interesting for anybody on our team or relevant to get work done on our project.

Describe the solution you'd like

A simple bool on the MRTK Lifecycle Manager component switching off debug logs would suffice since we don't need these logs to get any work done. Errors and warnings from the MRTK Lifecycle Manager should not be affected by this.

Describe alternatives you've considered

We could filter out all debug logs in the console but then we'd miss debug logs from our own systems (which can already be enabled and disabled per component instance).

We could also change the source code ourselves and alter the package's tarball file but we'd have to do that for every new MRTK release.

[AMollis]

Make sense. Would be a nice to have. We can look into making this configurable.