chore: Use pinned and forked versions of actions

[Gu1nness]

🏷 Type of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update
• Tooling and CI changes
• Dependencies upgrade or change

📝 Description

Following the GH actions corrupted payload, we fork and pin all versions of the actions.

📑 Motivation and Context

Security.

🧪 How Has This Been Tested?

✅ Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.