Android stability fixes

[gwen2018]

fixes pipeline.stop() crash issue and camera app performance/stability issues::

1. fix pipe.stop() issues
   a) problem: null pointer segfault
   cause: thread synchronization in dispatcher
   fix: add additional lock in invoke_and_wait.

b) problem: invalid address segfault in uvc_streamer, active_object, dispatcher flows
cause: double release of memory in destructors due to synchronization issue in watchdog, active_object, dispatcher, and
primarily uvc_streamer.
fix: add additional state check and synchronization.

c) problem: invalid address segfault in pipeline flows
cause: double release of memory in pipeline destructor to stop pipeline twice, the extra stop come from JNI code when handle is deleted and invokes destructor which tries to run stop() again.
fix: do shared pointer reset when profile active (also this is when they are initialized).

d) problem: invalid address segfault at various points depends on workload
cause: uvc_streamer shared pointers cleared at the wrong time, not cleared when stream stopped, so it tries to stop the
streamer a second time during destruction
fix: destroy uvc_streamers after stream is stopped and no active profiles

e) problem: invalid address segfault in device info destructor through JNI stack
cause: appears to be double releasing as JNI stack references the pointer
fix: avoid delete in JNI, need to confirm it's released on native stack.

2. problem: invalid address segfault related to stream profiles
   cause: profile data array copy in JNI, jlong is 64-bit but pointer could be 32-bit, should not xcopy the entire buffer
   fix: copy array elements

3. problem: invalid address segfault related to query sensors
   cause: sensor data array copy in JNI, jlong is 64-bit but pointer could be 32-bit, should not xcopy the entire buffer
   fix: copy array elements

4. problem: camera app performance degradation and stability issues after repeated device disconnect/connect (JIRA DS5U-4588)
   app cannot recover if device disconnected in middle of starting streaming
   cause: activity operations executed multiple times due to activity instances and sequence issue
   fix: create single activity instance, manage its creation and destruction, and correct sequence.

Tracked on: RS5-8219, DSO-15293, DSO-15294, DSO-15358, and DS5U-4588

[ev-mp]

@gwen2018 , a very thorough analysis and work. Nicely crafted.
Much appreciated!