Android memory cleanup and optimizations

[m4gr3d]

Miscellaneous set of code / memory cleanup and optimizations for the Android platform:

• Disable sensor events by default. Sensor events can fire at 10-100s Hz wasting cpu and memory resources if the sensor data is not being used. Now the use of sensor data is behind a project setting allowing projects that need it to enable it, while other projects don't have to pay the cost for a feature they don't use.

• Returns an empty list when there's no registered plugins, thus preventing the creation of spurious iterator objects

• Inline Godot#getRotatedValues(...) given it only had a single caller. This removes the allocation of a float array on each call

• Create a pool of specialized Runnable objects to dispatch input events and prevent spurious, unbounded Runnable allocations

• Disable showing the boot logo for Android XR projects

• Delete locale references of jni strings

[m4gr3d]

Disable sensor events by default. Sensor events can fire at 10-100s Hz wasting cpu and memory resources if the sensor data is not being used. Now the use of sensor data is behind a project setting allowing projects that need it to enable it, while other projects don't have to pay the cost for a feature they don't use.

@BastiaanOlij FYI, sensor events will be disabled by default following this PR. This may constitute a breaking changes for mobile VR projects. I've added some warning logs for debug builds to help identify the issue for those projects.

[BastiaanOlij]

Disable sensor events by default. Sensor events can fire at 10-100s Hz wasting cpu and memory resources if the sensor data is not being used. Now the use of sensor data is behind a project setting allowing projects that need it to enable it, while other projects don't have to pay the cost for a feature they don't use.

@BastiaanOlij FYI, sensor events will be disabled by default following this PR. This may constitute a breaking changes for mobile VR projects. I've added some warning logs for debug builds to help identify the issue for those projects.

Should indeed be easy to have a warning if the MobileVRInterface is used. While you're add it, a long outstanding wish has been to be able to influence the sensor accuracy which by default is set to be more laggy and less noisy. This is great when used for your normal phone applications but not in a VR settings.
I had an old PR that was closed due to it growing stale: #22644, might be worth revisiting.

[m4gr3d]

Should indeed be easy to have a warning if the MobileVRInterface is used.

I've added the warning when the getter for the sensor data is used while sensors are disabled, so that should cover both MobileVRInterface projects and projects using sensor data for other functionality.

While you're add it, a long outstanding wish has been to be able to influence the sensor accuracy which by default is set to be more laggy and less noisy. This is great when used for your normal phone applications but not in a VR settings.
I had an old PR that was closed due to it growing stale: #22644, might be worth revisiting.

Should be straightforward to add; I'll keep it in a separate commit.

[akien-mga]

Thanks!