To make the pipeline graph more semantic

Introduces CI for android-support crate, reorganizes pipeline structure and segregates ci scripts for android-components

Refactored the FFI Layer and the rust library now perfectly links to the android application right from initial start of the application

android: Delete automatically generated file and add dependence of child pipelines on android CI job

Even though the tests bind to different ports, it doesn't seem
possible to actually run them at the same time.  We will need to
investigate this!

Some of the internals of alexandria must be changed in line with
changes to the requirement scope of what it needs to be able to
handle.  Check issue #12 for details!

Ideally this is the first of many commits to clean up the storage
subsystem (there should be no `store` module required).  Certainly #4
will help with this!

Previously each service had access to many key-value stores, exposed
via the `MetadataMap` type.  The problem with this approach was that
services were responsible for differentiating between insertions and
updates, because this is a distinction that Alexandria enforces.

This API now exposes a single key-value store per service, with three
function endpoints as documented in #7: insert, delete, and query.
Insert acts as an upsert variant, which will either insert or update a
single key in the key-value store associated to the service.

In order to allow services to better namespace their data the key type
is `StoreKey`, a 2-string tuple which provides a namespace, alongside
a data key