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

We used the Atlas extension to generate a site-manifest.json. This file will be zipped and pushed to the same place as the site.
In the next step, we want to use these files to validate the xref linked in the content

This PR is inspired by #575.

Changes
- Configure Antora to handle latest/next
- Manage the versions pass to DocSearch: create a custom Antora
extension to pass new information to the bonita-documentation-theme
- Remove netlify redirects that are now managed by Antora (latest and
next)
- Update the "documentation test resources" to ensure we 
- GH Action: 
- the preview url for the PR comment now uses latest to match the url in
the surge preview
- fix an error in the shared action that prevented to compute the
preview url for the PR comment
- documentation: add a paragraph about how Antora caches the git
repositories and the ui-bundle

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

Historically, the preview script was directly called by a lot of GitHub
workflows. To avoid to duplicate the `npm ci` setup and ensure that
Antora fetches sources, it was easier to do it in the script.
Now, all documentation content repositories use the GitHub actions
provided by the bonita-documentation-site repository, so the extra
settings can be managed by the shared actions.

This move provides a better separation of concerns. The script only
focuses on generating the preview without managing special cases
depending on the environment. The `npm ci` command is called directly in
the `build-setup` internal action, where everybody expects to find it.
This allows to introduce the usage of the GitHub cache for the npm
dependencies, so we can expect fastest builds.
This also ensures consistency between the build and publish PR preview,
and the "publishing to production" workflows that are no more doing `npm
ci` in a different way.

In addition, we now run and advice to run Antora via `npx` as suggested
by the Antora documentation.

Remove remaining links to Antora 2.3 except for the Mardown to AsciiDoc migration as it applies to this Antora version.
To simplify future maintenance, use an AsciiDoc attribute to avoid duplicating the version.
Some links that were redirected to renamed pages have been updated.

* add bonita 7.4 out of support
* add paragraph about supplemental ui files
* test-toolkit: remove real content and use a fake one and add custom message

Provide document content directly in the project for testing purpose. The site
is fast to build with this content.
It lets test UI bundle change, Antora upgrade, site structure and much more.
It is also possible to build the site with the Antora Default UI for comparison
with the Bonita Theme.

* Add action (with cron all night)
* Use bash script comes from internal-tools
* Update documentation
* Add important citation in notification
* Use badge in README.adoc

The repository has been renamed, so update the url.

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

Co-authored-by: Adrien <adrien.lachambre@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)

This is now 'bonita-documentation-site'.

Use the non-production navbar:
  - dedicated title and background color
  - no search

The preview bash script now allows to
  - force usage of the production navbar
  - use locally built ui-bundle
The 'title' option has been renamed into 'site-title' for consistency

Previously, there were both bash and npm scripts that rely on several nodejs
script. For simplicity, we only have a single bash script that support all
existing options (with a single nodejs script).

The documentation has been improved
  - introduce `--help` in the bash script to display all available options
  - the README better explains how to generate the preview for both development
  and deployment

Bonus: activate Admonitions with github support in the README

Generate an Antora Playbook from the regular one and change the content sources
configuration.

* Document when we need using local sources git repo

Integrate the BICI migrated content and document how this has been done for reuse with other content (based on previous poc).
The antora-ui bundle has been generated from a previous poc, it will be updated with content of bonitasoft/bonita-documentation-theme later

This also setup
    - build with npm: shared commands and shared dev/build setup
    - antora playbook: more ready for GH pages deployment
    - allow to build the site for local and production usage
    - allow to run local http server for evaluation