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