Fix/4401

[Remi-Gau]

• Closes #

Changes proposed in this pull request:

-

Summary by Sourcery

This pull request introduces a new GitHub Actions workflow to automate the triggering of documentation hosting jobs on CircleCI. It includes a script to manage the triggering process, ensuring the correct branch and pull request number are used.

• CI:
  • Added a new GitHub Actions workflow to trigger documentation hosting jobs on CircleCI after the 'Documentation builder' workflow completes.
  • Included a script to handle the triggering of CircleCI jobs, with logic to determine the appropriate branch and pull request number.

[sourcery-ai[bot]]

Reviewer's Guide by Sourcery

This pull request addresses issue #4401 by implementing a new workflow to trigger the hosting of documentation on CircleCI after the documentation build completes successfully. The changes include modifications to the existing GitHub Actions workflow and the addition of new scripts and workflows to facilitate this process.

File-Level Changes

Files	Changes
.github/workflows/build-docs.yml .github/workflows/trigger-hosting.yml	Updated and added GitHub Actions workflows to trigger documentation hosting on CircleCI after successful documentation build.
build_tools/github/trigger_hosting.sh	Added a new script to handle the triggering of CircleCI jobs for hosting documentation, including logic to determine the branch and pull request number.

---

Tips

- Trigger a new Sourcery review by commenting `@sourcery-ai review` on the pull request. - You can change your review settings at any time by accessing your [dashboard](https://app.sourcery.ai): - Enable or disable the Sourcery-generated pull request summary or reviewer's guide; - Change the review language; - You can always [contact us](mailto:support@sourcery.ai) if you have any questions or feedback.

[github-actions[bot]]

👋 @Remi-Gau Thanks for creating a PR!

Until this PR is ready for review, you can include the [WIP] tag in its title, or leave it as a github draft.

Please make sure it is compliant with our contributing guidelines. In particular, be sure it checks the boxes listed below.

• [ ] PR has an interpretable title.
• [ ] PR links to Github issue with mention Closes #XXXX (see our documentation on PR structure)
• [ ] Code is PEP8-compliant (see our documentation on coding style)
• [ ] Changelog or what's new entry in doc/changes/latest.rst (see our documentation on PR structure)

For new features:

• [ ] There is at least one unit test per new function / class (see our documentation on testing)
• [ ] The new feature is demoed in at least one relevant example.

For bug fixes:

• [ ] There is at least one test that would fail under the original bug conditions.

We will review it as quick as possible, feel free to ping us with questions if needed.