Extract frontend components in a separate library

Once the data provider and auth provider will [support "regular" Solid servers](https://github.com/assemblee-virtuelle/semapps/issues/1121), the frontend components will be usable by any Solid developers.

I think it's the good time to split the backend services and frontend components from SemApps, which cause confusion, since it make people believe that the two need to be used together.

So I propose to keep "SemApps" as the name for backend services, to find a new name for frontend components and to move the [frontend documentation](https://semapps.org/docs/frontend) to a new [Starlight](https://starlight.astro.build/fr/)-based website.

**What name shall we use ?**

Ideas:
- Linked Data Framework (but already used [here](https://docs.plm.automation.siemens.com/content/polarion/20/help/en_US/teamcenter_polarion_integration_installation_43/solution_components/configure_the_teamcenter_linked_data_framework_ldf_component/overview.html) ... besides LDF is also the acronym for Linked Data Fragments)
- FI-LD (Framework for the Integration of Linked Data)
- ...

Ping @simonLouvet @fluidlog @VincentFarcy @GuillaumeAV (we are requesting funds from NLnet for this issue, amongst others)

## Related issues

- https://github.com/assemblee-virtuelle/semapps/issues/1218

Start by reviewing related issues 1121 and 1218, then inspect the existing frontend documentation at semapps.org/docs/frontend and the current frontend components. The work is complete when the frontend components have an agreed separate library and the documentation has moved to a new Starlight-based website.

Written by the indexing model from the issue text.