[Feature]: Enable screener checks to run from the screener proxy

[ralucapelin]

Library

React Components / v9 (@fluentui/react-components)

Describe the feature that you would like added

Make screener checks runs to be triggered by the screener proxy instead of ADO using the GitHub API.

• Convert the Azure DevOps job that runs the screener checks to a GitHub Action; | Add screener workflows #24106
• Remove ADO jobs regarding screener checks; | Enable screener workflows #24178
• Trigger screener checks using the GitHub REST API.

Have you discussed this feature with our team

@ling1726

Additional context

No response

Validations

• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[ralucapelin]

-forks don't have access to the repo's secrets, so the workflow wouldn't work if triggered by forks
-solution: use two workflows -> one creates necessary artifacts that do not require access to secrets and is run from the fork
-> one uses information from the two artifacts and is run from the repo