feat: generate new version of doc for each release

[ijemmy]

Description of your changes

• Rename version develop to main
• When release, it will have the release version (e.g. 0.1.0 ) with the alias latest. It also set latest as the default version when user go to the root.

How to verify this change

I verified by changing the target trigger branch and push my change there. The run was green and new version of doc has been published.

Related issues, RFCs

PR status

Is this ready for review?: NO
Is it a breaking change?: NO

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• The code coverage hasn't decreased
• I have added tests that prove my change is effective and works
• New and existing unit tests pass locally and in Github Actions
• Any dependent changes have been merged and published in downstream module
• The PR title follows the conventional commit semantics

Breaking change checklist

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[saragerion]

LGTM

[dreamorosi]

Thanks for the PR.

[flochaz]

I am not sure it's going to work ... this version will be the one before ... the on-release workflow will bump the version and push a new commit with the new version in package.json as well as a corresponding git tag. And this commit skip ci to avoid infinite loop ... I think we should make this run only if the on-release succeed or move those jobs in the on-release workflow