Cover https://github.com/bonitasoft/bonita-documentation-site/issues/588

Remove duplicated anchor.
Add missing close block.
Also remove extra trailing spaces.

Works around issue https://github.com/asciidoctor/asciidoctor/issues/3128

closes [RUNTIME-969](https://bonitasoft.atlassian.net/browse/RUNTIME-969)
closes [RUNTIME-1652](https://bonitasoft.atlassian.net/browse/RUNTIME-1652)

chore(deps-gha): bump calibreapp/image-actions from 6753df48e658313f05436f016de5592677300659 to 20f376152ba330053aaf2f53342654551348df16 (#2313)

Typo error in the Compound permissions mapping section. 
By default, the file, the name of the file is
"compound-permissions-mapping.properties" not
"resources-permissions-mapping.properties".
Ideally, in this section, we could update it with use cases section to
demonstrate some permissions capabilities.

Clean syntax of the java examples (format and add semi-column).
Fix the syntax of an url extract: remove a dangling `+` character and use the appropriate AsciiDoc
syntax for italic.

In this PR will be included pages in which text or context improvements
have been made.

Update database-configuration doc on wrong Oracle SQL queries proposed
to create the 2 schemas for Bonita.

"identified by xxx" section in the 1st GRANT comment is not correct.
It must be removed.

Typo error on "TO bonitbusiness_dataa;" must be replaced by "TO
business_data;"

Co-authored-by: Valentina BOTNARI <89633642+vbotnari12@users.noreply.github.com>

simplify documentation as for these 3 files the only differences would
be in comments

---------

Co-authored-by: Valentina BOTNARI <89633642+vbotnari12@users.noreply.github.com>

add proper path to tenant_portal config

* The api documentation is available on a external website

Based on customer case we've got (00027068 -
https://bonitasoft.lightning.force.com/lightning/r/Case/5002p00002pUaATAA0/view

),
we are adding a new troubleshooting section for all customers that may
face the same issue.

Co-authored-by: vbotnari12 <89633642+vbotnari12@users.noreply.github.com>

The new compress-images workflow is launched when an image is added or
changed.

Covers bonitasoft/bonita-documentation-site#434

Covers [UID-717](https://bonitasoft.atlassian.net/browse/UID-717)

Update done according to the new troubleshooting format proposed by R&D.

Co-authored-by: vbotnari12 <89633642+vbotnari12@users.noreply.github.com>

listing all the editions is unnecessary especially because we are
selling only Enterprise now.

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

Update rest-api-extensions doc according to new troubleshooting format.

Co-authored-by: vbotnari12 <89633642+vbotnari12@users.noreply.github.com>

Co-authored-by: abirembaut <anthony.birembaut@bonitasoft.com>
Co-authored-by: vbotnari12 <89633642+vbotnari12@users.noreply.github.com>

Use the v2 tag for auto-update.

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

Co-authored-by: Bishal Thapaliya <vishal.thapaliya@gmail.com>

… 2021.1

<!-- 
Insert your contribution description here.
Ensure your contribution fills the Contributing Guidelines described
here, in particular, give a special attention to the TITLE format:

https://github.com/bonitasoft/bonita-documentation-site/blob/master/docs/content/CONTRIBUTING.adoc


-->

Insert your Pull Request description here...

* add support for ...
* fix ... behaviour
* refactor ....

Co-authored-by: Bonita CI <bonita-ci@bonitasoft.com>

Please find updates on the troubleshooting section for
bonita-bpm-studio-installation doc according to the new troubleshooting
format.

Update the troubleshooting section by using the new format

They have been automatically generated during the Markdown to AsciiDoc
conversion but are not relevant. For the record, the comments was
generally something like `// {.img-responsive}`.

covers
https://github.com/bonitasoft/bonita-documentation-site/issues/458

Versions: 2021.1, 2021.2, 2022.1, 2022.2

Change the troubleshooting tip format from old to the new one.

Co-authored-by: abirembaut <anthony.birembaut@bonitasoft.com>

It marks the workflow as failed whereas it is set to provide help to
contributors.
All Pull Requests are currently marked in error: disable the action
until we find a way to fix the problem/

Do not check
  - the PR title when pushing new code
  - the "file changes" when editing the PR title

Also run all jobs of the workflow on Ubuntu 22 and when the PR is
`reopened`.

The Vale action was set to 'reviewdog' branch by error. It is not stable
and the action failed to run from time to time.

In addition, restore permissions for the 'pr-title' job that was removed
by mistake in c2e10ec6.

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