* reword the existing sections
* add 2 additional information: subsections and grey areas

Co-authored-by: Thomas Bouffard <27200110+tbouffard@users.noreply.github.com>

The repository has been renamed, so update the url.

Antora now generates the `_redirects` file for aliases, so update the doc
accordingly.

We are only checking the PR title and description so we don't need to checkout (we are not considering the repository code here).

Let us list and teardown deployments.

Covers #178 

* gh workflow: use internal 'build setup' custom action
* Update package-lock.json for npm 8 (node 16)
* Update doc + let configure nvm

add Troubleshooting section formatting guidelines

* The former redirect haven't worked anymore since the introduction of Antora modules.
* Update redirects for old bonita versions

Redirect all old versions and non version url to latest.
This reduces maintenance when releasing a new version.

Aliases are now generating true http 301 instead of http 200 via http page; this
will be better for SEO.
Update the 'type' argument to enable it for preview.

`/next` will redirect to `/1` (aka the alpha version) without changing the URL. 
The main url is - and will remain - `/1`, because it allows us to ensure that the dev version is sorted correctly among other versions (at the end). So a user that go to the alpha version through the menu will have the URL `/1`. But at least, with this redirect, if we want to send a link to a client we can do it with `/next`, which is a bit better.

Co-authored-by: Adrien <adrien.lachambre@bonitasoft.com>

Co-authored-by: Benjamin Parisel <benjamin.parisel@bonitasoft.com>

* Update old BCD redirects
Old version are redirected to BCD 3.4 and not latest (last version with BCD stack).
* Update netlify.toml

Add a step by step procedure to ensure that everybody will be able to test redirects easily.

* update UI bundle
* remove the custom extension (we didn't went for this solution)

Don't put a version in the configuration and let Antora use the latest version to reduce the maintenance cost.
Setting the version has been needed in the past when we have introduced the Bonita archives; it required to
use custom versions ordering and the 2021.1 were not considered as the latest version.
We have switch back to the default ordering, so this extra configuration is not needed anymore.

Co-authored-by: Thomas Bouffard <27200110+tbouffard@users.noreply.github.com>
Co-authored-by: Adrien <adrien.lachambre@bonitasoft.com>
Co-authored-by: hugues.bretin <hugues.bretin@bonitasoft.com>

Improvements
  - enforce 'redirect' and 'no fetch sources' config except if explicitly
  requested
  - allow to build all components/branches using a new `use-all-repositories`
  option
  - allow to build a set of components and branches with new options
  (`use-multi-repositories` and `component-with-branches`)
  - add a dedicated bash preview script for local developments. Everything can
  now be done with the script so specific npm scripts have been removed from the
  package.json file
  - new bash script option to skip the doc generation and only generate the
  Antora preview playbook
  - improve the site title management logic
  - allow to use boolean options without having to pass 'true' as argument

Fixes
  - allow the bonita '7.10' branch build
  - make the 'fetch sources' option work

Readme updates
  - reorganize to put end-user documentation first
  - put local developments information first as this is what developers mainly
  use
  - provide more details about the `build-preview` bash script usage (for
  instance http server and asciinema)

[WWW-982]

* Add bonita cloud admonition