Don't keep the LibreOfficeKit pointer in a global variable

It is invalid in case lo_destroy() has been called.

Change-Id: I45533b66d32fc650e48748da8ea1d2f2aaa381e0
The 'bInitialized' state needs to be global, and unset in lo_destroy()

I assume, for lo_destroy() to be useful at all. Not that I know for sure what
the exact intended semantics of lo_destroy() and lo_initialize() are. But I
assume that the idea is that after lo_destroy() has been called,
lo_initialize() can be called again.

Change-Id: I2dea26db150d19ed438427e1c119a5297b9bc9c3
Skip the 'desktop' app for now

Change-Id: I040bd49f8cfeec74c3225135a110140c1816be43
Call DetachCurrentThread() in the AndroidSalInstance destructor

As we call AttachCurrentThread() in the constructor, it seems logical to call
DetachCurrentThread() in the destructor. Some warning messages in the logcat
indicated that DetachCurrentThread() hadn't been called for a thread that
died.

Actually I would prefer to call both AttachCurrentThread() and
DetachCurrentThread() in the actual thread function, instead of somewhat
haphazardly and imlicitly in the AndroidSalInstance constructor and
destructor. Do we know for sure that the lifetime of the AndroidSalInstance
singleton (is is a singleton, right?) is 1:1 coupled to that of the LO "main
thread"?

Change-Id: Ifcc0e0b9af88b19389c416c5646499d44ad0e941
If loading a document fails, try restarting the 'main loop' and try again

Does not work, though, we end up with a crash that is hard to debug thanks to
the rubbish tool-chain.

Change-Id: Ie1954e35e649fac8dd106f0ccbc6951c4a6c1c63
Add a small script to run adb logcat with filtering

We use arbitrary tags when logging stuff in our code so we can't use the
built-in filtering of adb logcat.

Change-Id: I2d607b86bde975c5cbdd17adc22d0fc15076be51
Reduce log verbiage

Change-Id: I0da75df61d129aaaf03ac546fcf1e5dbcff9d404
Use maximum logging verbosity while attempting the restart

Change-Id: I3e3162474db1edef3b92e252b249fe373dedbbfd
Add a SAL_INFO

The "bootstrap" errors tend to end up being displayed in some error dialog
attempt which of course does nothing on mobile platforms, and that crack seems
to crash on Android even, so this should give us some chance to get some idea
at least what the code thinks is wrong...

Change-Id: I070b017baf042ff692766d1efd1511e1addb6ecf