Wrong callback to JmeSurfaceView#destroy()

[Scrappers-glitch]

As i recall, app.destroy() is called back by the system listener which is governed by application listeners, in this case there is a duplicate call to destroy() :

1. jmonkeyengine/jme3-android/src/main/java/com/jme3/app/jmeSurfaceView/JmeSurfaceView.java

   Line 363 in 3d979df

   destroy();

2. jmonkeyengine/jme3-android/src/main/java/com/jme3/app/jmeSurfaceView/JmeSurfaceView.java

   Line 507 in 3d979df

   legacyApplication.stop(!isGLThreadPaused());

There should only be app.stop() which will naturally dispatch the context.destroy().

The proposed fix should move the legacyApplication.stop(!isGLThreadPaused()); to the ON_DESTROY instead of the direct call to destroy() and should call legacyApplication.destroy() inside the destroy().

[stephengold]

@Scrappers-glitch Will you provide us with a PR?

[Scrappers-glitch]

Yeah sure, i will do a PR at the end of this week.