Decouple auto-rotate issue logging and refactoring code

Currently the logging logic is in trunkfood full while refactor logic is still in developement.
The code is coupled in such a way that some of the refactor logic heavy classes would be instantiated when logging flag is enabled.
It would be best to decouple them and avoid instantiating classes that are still under development.

This change also has moved the instance creation of certain classes to RootWindowContainer from DisplayRotation.
There can be multiple instances of DisplayRotation based on number of display, while we want singleton instances of these classes.
Now that we will have singleton instance of auto-rotate issue logger, it would also solve the issue of duplicate logging of auto-rotate issue.
Next CL: Implement DeviceStateAutoRotateSettingController

Fixes: 402764691
Test: atest DeviceStateAutoRotateSettingIssueLoggerTests
Flag: com.android.window.flags.enable_device_state_auto_rotate_setting_logging
Flag: com.android.window.flags.enable_device_state_auto_rotate_setting_refactor
Change-Id: I0432f0575fc10c038320e9d5c2b41ec5557eca48