Migrate azure-dev repo to use the new Check Enforcer and decommission the obsolete CheckEnforcer tool

[konrad-jamrozik]

Current Check Enforcer tool is a GitHub action living in azure-sdk-actions repo.

However, there is also an obsolete Check Enforcer in use, which should be decommissioned. I made a PR doing that here:

• Delete obsolete CheckEnforcer tool #4963

Turns out, we cannot delete it yet, as it is being used, at least by azure-dev repo. To migrate azure-dev to use the new Check Enforcer, we need to update the workflows in azure-dev repo to call into the GitHub action-based Check Enforcer workflow, .github/workflows/event.yml.
For details and alternative approaches we considered, see that PR's discussion, especially the Teams discussion linked from this comment.

Once we migrate azure-dev to the new Check Enforcer, we should decommission the old Check Enforcer by doing the following:

• delete the source code and pipeline as proposed by Delete obsolete CheckEnforcer tool #4963;
• delete all eng/CHECKENFORCER files; CHECKENFORCER files are per-repo configs for what the help comments Check Enforcer made should read. These now live in the azure-sdk-actions repo and are no longer customizable on a per-repo basis;
• update all docs to point to the new Check Enforcer.

Once we decommission the old Check Enforcer, we now should be able to also decomission WebhookRouter tools, as captured by this issue:

• Decommission all WebhookRouter tool downstream consumers and then the tool itself #4992

[kurtzeborn]

You should be unblocked on this now. These are done:

• delete all eng/CHECKENFORCER files; CHECKENFORCER files are per-repo configs for what the help comments Check Enforcer made should read. These now live in the azure-sdk-actions repo and are no longer customizable on a per-repo basis;
• update all docs to point to the new Check Enforcer.

[konrad-jamrozik]

You should be unblocked on this now. These are done:

• delete all eng/CHECKENFORCER files; CHECKENFORCER files are per-repo configs for what the help comments Check Enforcer made should read. These now live in the azure-sdk-actions repo and are no longer customizable on a per-repo basis;
• update all docs to point to the new Check Enforcer.

I asked question related to that here:

• Decommission all WebhookRouter tool downstream consumers and then the tool itself #4992 (comment)

[konrad-jamrozik]

Per this comment and my discussion with @benbp, I will delete the no longer used Azure resources related to CheckEnforcer. The exact list of resources I am going to delete is listed here, on Azure SDK / Engineering System Teams channel.

Update 1/25/2023 10:40 PM PST: I have deleted the resource groups.

[benbp]

@weshaggard we could also go in and delete the github app, but I'm wondering whether we want to keep it around for future use given the steps it takes to onboard an app into azure (though I'm not a fan of continuing to use the old name).

[weshaggard]

I think the app is also shared with webhook router for the same reasons of setting up is costly so we should probably keep the app around until we decommission that as well.