Split up JSLib from k6-docs repository for versioning purposes

[heitortsergent]

Related to #1979.

JSLib is a set of utility libraries that users can use with k6. Each library has its own set of versions. Currently, in the k6 OSS docs, we have a folder for each k6 version, but other projects are not versioned, including the JSLib libraries, the k6 Operator, and k6 Studio.

Should we consider splitting the documentation for these other projects so we can have docs for each version? What would that look like in grafana.com/docs? What would the workflow look like for updating these docs, and keeping them in sync?

[mstoykov]

so we can have docs for each version?

While that will be nice, it will also be nice if we do not have to have update the same docs for each k6 version. That currently seems like the bigger issue to me. Most jslibs are fairly rarely updated, if at all in the last years.

Having them versioned will be nice though, but not what I mainly asked for.