Put real bonitaTechnicalVersion in bonita-doc on each release

[benjaminParisel]

In life cycle of Bonita-doc, we get sometimes some 404 links. (ex: many link in this page https://documentation.bonitasoft.com/bonita/2022.2/identity/user-authentication-overview#_bonita_runtime_authentication_scenario)

It's because we put in antora.yml, the attribute bonitaTechnicalVersion to final tag value.
This attribute is used in some links to share code with our final user.

I suggest updating bonitaTechnicalVersion in bonita-doc repository each time we will do a release. It could be done buy an action in bonita-doc repository, and called her by HTTP rest directly in our release pipeline

It could help us later if we want to run a tool to detect our dead link for example.

• Create a githubaction on bonita-doc to update antora.yml
• Call this action directly in release-pipeline