CHORE: Add cooldown for github actions

[SMoraisAnsys]

Description

As title says. The feature is out of beta and now available for github actions too !

Issue linked

Related to #5524

Checklist

• I have tested my changes locally.
• I have added necessary documentation or updated existing documentation.
• I have followed the coding style guidelines of this project.
• I have added appropriate tests (unit, integration, system).
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved by the PR if any.
• I have agreed with the Contributor License Agreement (CLA).

[ansys-reviewer-bot]

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

@ansys-reviewer-bot review

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.24%. Comparing base (e6725d0) to head (d59ec18).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6327      +/-   ##
==========================================
+ Coverage   84.16%   85.24%   +1.08%     
==========================================
  Files         173      173              
  Lines       65294    65294              
==========================================
+ Hits        54953    55661     +708     
+ Misses      10341     9633     -708     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Samuelopez-ansys]

What is this?

[SMoraisAnsys]

What is this?

This adds a cooldown between the time dependabot opens a PR and the release date. Here we are expecting at least a week to be passed before dependabot propose us a change that let us use a new release. That way, if someone does perform a new minor version with a vulnerability (for python) or any new release for a github action, we might never be impacted because in between the release and dependabot's PR, the release might be removed or fixed.