[EC-399] Azure DevOps pipelines migrated into GitHub Actions

[mamu0]

List of Changes

The two workflows on Azure DevOps

• code-review
• deploy-pipelines

have been recreated in the form of GitHub Actions.

They have been inserted in the .github/workflows folder.

Added pre-commit configuration.

Added infra folder with identity and repository infrastructure, and added branch protection on master (already applied).

Edited .gitignore and CODEOWNER files.

Motivation and Context

Since all the pipelines on Azure DevOps are gradually being decommissioned, it was decided to recreate them on the different repos such as GitHub Actions.

How Has This Been Tested?

Currently they have been tested by inserting

push:
  branches:
    - EC-399-devops-decommissioning

so as to execute them automatically at each test push.
To do the Deploy test for deploy-pipelines action i've used this step only to check if all will be called correctly:

      - name: Deploy
        run: |
          az webapp up \
            --dryrun \
            --resource-group ${{ inputs.resource_group_name }} \
            --name ${{ inputs.app_name }} \

To do the Deploy test for publish-sdk action i've executed everything except last command with effective publish.

A real deploy test is needed.

Screenshots (if appropriate):

Types of changes

• Chore (nothing changes by a user perspective)
• 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 not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[github-actions]

Jira Pull Request Link

This Pull Request refers to the following Jira issue EC-399

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud