Feat/build native android apps with android solid services

[erfangholami]

Add a guide for native Android developers to integrate Solid into their apps with the help of AndroidSolidServices project.
It presents developers with two different methods for integration based on their use-case.

[jeswr]

Thank you for this contribution @erfangholami!

Before we merge, I ask that this library could be given a different short-name - even if just used in this documentation. I suggest SolidAndroidService (SAS).

The documentation on Authentication, and Read/Write are great contributions well-suited to this repository.

The documentation based around use of Data Modules warrants further discussion. There are divergent approaches to interoperability in the Solid ecosystem at present; as such, I would consider documentation related to Data Modules in general to be opinionated. The ODI, for instance, has propose the shapes repository as a way of tracking and aligning on data models used in the ecosystem. The fact that the Chat Spec is used as an example, does somewhat resolve this. My suggestion is that we keep this in the docs, and add clear warnings - here, and in SAS itself - about what is based on:

• Specifications (and, if so, identify the version no. & maturity of the specification referenced), here I expect you to need to reference:
  • https://solidproject.org/TR/2024/protocol-20240512
  • https://solidproject.org/TR/oidc (most likely publish snapshot of pre 0.1 version (spec+primer) solid-oidc#250 once merged)
  • https://solid.github.io/chat/
• Best practise / implementors knowledge; and where that knowledge comes from (I expect this to be anything else in the data modules)