Restore JmeSurfaceView android flow

[riccardobl]

I proposed a plan to include a CompatHarness fragment and activity that support Androidx and uses the JmeSurfaceView with very minimal code; as all the code and binding among the jMonkeyEngine application and android application lifecycles are handled within the surfaceview component...

Originally posted by @pavly-gerges in #2776 (comment)

[riccardobl]

Should build on top of #2774

[pavly-gerges]

I've developed the code in a separate library; the CompatHarness depends on the JmeSurfaceView, and uses abstract factory patterns to bind Android and jMonkeyEngine lifecycles.

If you agree to include these upgrades; I will submit a PR after restoring the surfaceview.

This is an example of the CompatHarness activity:

https://github.com/Electrostat-Lab/Game-HCI/blob/master/demoApp/src/main/java/com/myGame/JMESurfaceViewExampleActivity/compatTest/TestCompatHarness.java

This is the API code (Note this code also fixes the flycam input issues on Android using platform specific touch events):

https://github.com/Electrostat-Lab/Game-HCI/blob/master/SuperiorPlugin/src/main/java/com/scrappers/superiorExtendedEngine/jmeSurfaceView/compat/CompatHarness.java

[riccardobl]

Sure, please go ahead.
I don't know much about android backward compatibility patterns, but as long as it does not lock us to java 8 (everyone is asking us to upgrade to at least 11), it should be fine.

[pavly-gerges]

Do you still have flycamera issues on Android?

[pavly-gerges]

Yes, it's still an issue.

#68

Do you have any other ideas for this? the solution I added was to use platform-specific touch zones, and use an adapter pattern to dispatch the calls to the jMonkeyEngine thread.

[riccardobl]

I think this is mostly fixed by the virtual joystick #2803

[pavly-gerges]

Does the virtual joystick control the flycam by default? Afaik, the flycam needs to be bound manually to the input interface.