Use GitHub Actions

[VladislavAntonyuk]

Description of Change

Initial migration from Azure Pipeline to GitHub Actions.

Skipped NuGet publish.

Linked Issues

• Fixes #

PR Checklist

• Has a linked Issue, and the Issue has been approved(bug) or Championed (feature/proposal)
• Has tests (if omitted, state reason in description)
• Has samples (if omitted, state reason in description)
• Rebased on top of main at time of PR
• Changes adhere to coding standard
• Documentation created or updated: https://github.com/MicrosoftDocs/CommunityToolkit/pulls

Additional information

[jfversluis]

This is a great start!

I think we need two more things:

• signing
• releasing

Both of these I think will be very similar to what Windows does. They have stages already set up and the secrets they are using are org secrets, so those should be available to us.

We "just" need to check the conditions here and make sure that they match out release procedure with creating a git tag and then using the version number from that.

[GeorgeLeithead]

Can we check to see what code coverage reports we will get? Well we be getting similar to what we get from Azure DevOps?

Copilot reviewed 2 out of 3 changed files in this pull request and generated no suggestions.

Files not reviewed (1)

• .github/workflows/SignClientFileList.txt: Language not supported

[jfversluis]

Keeping the azure-pipelines.yml around for a little bit more until we know the GitHub Actions do everything they should. Mostly releases.

I can basically only test the sign and release part by actually doing a release and when that turns out to not work, I'd rather be able to revert back to Azure Pipelines to get the release out and fix it for a next time.