chore(enum-updater): split out workflows and fix combined changes issue

[paulhcsun]

Description of changes

1. Split out the part for updating the static mapping into a separate workflow which is run at 12am Monday.

2. Main workflow for actually updating the enums is set to run at 1pm Mondays and will not only rely on the existing static mapping instead of updating the static mapping before running the enum update script.

3. Also main workflow will reset all changes before creating a new PR for a separate module to fix the issue where PRs were created with combined changes from previous modules.

4. Fix open PR check by title - search for chore(...) instead of feat(...)

5. Add logging

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[moelasmar]

this step needs to move the other workflow, so we will only create a PR if there is changes to the static mapping file, or we do not need to push any prs

[moelasmar]

actually, it is already in the other flow, so it should be removed from this one

[moelasmar]

I ment this section static-mapping-check

[moelasmar]

thanks Paul, I left some comments

[paulhcsun]

@Mergifyio update

[mergify]

update

❌ Mergify doesn't have permission to update

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/github-merit-badger.yml without workflows permission

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 5758508
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.