build: update action versions in CI workflows to latest stable releases

[germa89]

Description

As the title

Issue linked

Related to ansys/actions#814

Checklist

• I have visited and read Develop PyMAPDL.
• I have tested my changes locally
• I have added necessary documentation or updated existing documentation.
• I have followed the PyMAPDL coding style guidelines.
• I have added appropriate unit tests that also ensure the minimal coverage criteria.
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved to the PR if any.
• I have assigned this PR to myself.
• I have marked this PR as draft if it is not ready to be reviewed yet.
• I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

Summary by Sourcery

CI:

• Update ansys/actions/doc-deploy-changelog, check-pr-title, doc-style, build-wheelhouse, check-vulnerabilities, build-library, release-github, doc-deploy-stable, doc-deploy-dev, hk-package-clean-untagged, and doc-changelog actions from v9 to commit 2cf9a9c43235a000d613c2b13e64c954232a4553 (#v9.0.9) in CI, docker cleanup, and labeling workflows.

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[sourcery-ai]

Reviewer's Guide

Pins all ansys/actions usages in GitHub workflows to the exact v9.0.9 commit hash to ensure stable, reproducible CI runs.

File-Level Changes

Change	Details	Files
Pin CI workflow actions to specific v9.0.9 commit	Bump doc-deploy-changelog action Bump check-pr-title action Bump doc-style action Bump build-wheelhouse action Bump check-vulnerabilities action Bump build-library action Bump release-github action Bump doc-deploy-stable action Bump doc-deploy-dev action	.github/workflows/ci.yml
Pin docker cleanup workflow action to v9.0.9 commit	Bump hk-package-clean-untagged action	.github/workflows/docker_clean_untagged.yml
Pin label workflow changelog action to v9.0.9 commit	Bump doc-changelog action	.github/workflows/label.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @germa89 - I've reviewed your changes - here's some feedback:

• Consider using the official semantic version tag (e.g., @v9.0.9) instead of raw SHAs for better readability and easier future updates.
• You could DRY up these workflows by extracting the repeated action version into a shared variable or central config to simplify future bumps.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.27%. Comparing base (a1a20bc) to head (6da61fd).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3920      +/-   ##
==========================================
- Coverage   88.28%   88.27%   -0.01%     
==========================================
  Files         187      187              
  Lines       14830    14830              
==========================================
- Hits        13092    13091       -1     
- Misses       1738     1739       +1     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.