Move Browser SDK documentation to a proper place
Problem
Currently, the documentation for the SDK package is within the Readme file in the SDK directory. This is not easily found by someone who just wants to set up the SDK.
Additionally, there is a vitepress setup configured in the main package.json file of the library and the docs are build this way as well, but not actually used.
Desired Outcome
We clearly understand where usage documentation for this (and any other) Product Analytics SDK should live. Other approaches are cleaned up and the docs are moved to the appropriate place.
Potential Solution
Move the docs to docs.gitlab.com, since this is where all other docs around using Gitlab live and where users expect them to be. An open question is whether we can put them into one folder other Product Analytics content.
Nav structure proposal:
- Analyze application performance
- Quick Start
- SDKs
- Browser
- Ruby
- ...
- Product Analytics