Extensions workflow tests improvements

[aalves08]

Summary

Fixes #

Occurred changes and/or fixed issues

• fix script permissions in master extensions workflow tests that prevented it from running successfully
• change extensions workflows tests titles so that they are not confusing when browsing github actions UI
• add condition for extensions workflow tests not to run on forks
• improve slack message job on extension workflows to handle "empty" status of jobs

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[jordojordo]

lgtm - Just curious, what would cause a "No job status"?

[aalves08]

lgtm - Just curious, what would cause a "No job status"?

A script not running because of permissions on the file 😛 It doesn't exit the job with either a success nor a failure apparently
https://github.com/rancher/dashboard/actions/runs/12287118973

Check the slack message job to see the echo's