[WIP] Add versioning capabilities for our documentation

[gagnonanthony]

Once we start making new releases of nf-neuro, we should be able to version our documentation to keep track of when changes happen. This PR sets it up it will look like this:

However, there are a couple of things to fix before merging it:

• Fix small typos in some meta.yml files that break the site's build. (Fix meta for proper build of documentation site with versioning modules#131)
• For some reason, the plugin is not setting the route correctly on old versions on the landing page. I opened an issue here (Wrong link from index page when using a base in documentation site HiDeoo/starlight-versions#20)
• We will need to decide how to handle the modules and subworkflows between versions. My suggestion would be that once we make a release, we archive the current state of modules/subworkflows in a version. The latest version will be updated as it is now (dynamically).

@AlexVCaron @arnaudbore

[AlexVCaron]

We could use the repo releases to save the state of the whole documentation at a given version (or latest if no version) when we build it. The coalesed versions can be saved either in the workflows cache or in an artifact, if a version tag is given. Then, when we build the site for deployment, we simply patch the build with the cached content.

[AlexVCaron]

Also, the version tag should come from nf-neuro. When we create a new version there, we automatically create and tag a new version of the documentation here and everything aligns.