We don't have component using the 'bonitaAPI' component.name. So, there is no
reason for filtering such component in nav and toc.
This seems to be a remaining part of the POC done in 2020: we were trying to
integrate the Bonita API documentation within the site. We don't have such API
in the site for now.

Sub-folders were taken into account.

We do not increase the font weight on hover (in the nav, the toc...) -> no more 'flash' effect
Add a dedicated color for hover, so the contrats is better on light theme

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

* update package-lock.json
* build-setup action: run 'npm ci' to avoid duplications in workflows
* doc update for Node 16

Use a dediacted color in light theme for links in admonitions, so it is visible in all admonitions. (#64)

Revert "Downgrade higlight.js version and use old function notation to be ie11 compatible (#58)" (#59)

This reverts commit bd7a0eb7.

* Update bold policy and dark higlight color

* update color

relates to https://github.com/bonitasoft/bonita-documentation-site/issues/211

This is now 'bonita-documentation-site'.

We don't want to display such links in documentation archives we want to make
available for download only.
In this case, the documentation content source code is not available locally
so keeping the links is just misleading.

For single component version archive, this is not need as we have a single
component. In addition, the link produced for component in this list doesn't
work for local file browsing.

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

Use old instead of the for the version