Maintenance: remove PR automation based on workflows

[dreamorosi]

Why is this needed?

We have made updates to the Powertools OSS Automation app that allows us to label issues linked to a PR once the PR is closed (among other automation tasks). Because of this, we can remove the bespoke workflow-based automation that did the same thing but with extra steps. This simplifies our CI/CD infrastructure, reduces maintenance burden, and eliminates 838 lines of unused code across 15 files.

Which area does this relate to?

• Automation

Solution:

Remove the following unused GitHub workflows and associated scripts:

• record_pr.yml - Core PR data collection workflow
• on_opened_pr.yml - New PR validation
• on_merged_pr.yml - Post-merge automation
• on_label_added.yml - Label-based actions
• reusable_export_pr_details.yml - Reusable PR data export
• label_pr_on_title.yml - Auto-labeling based on title
• dispatch_analytics.yml - Analytics dispatch workflow
• Associated JavaScript files in .github/scripts/

This cleanup has already been implemented in branch cleanup/remove-pr-automation-workflows and is ready for review.

Acknowledgment:

• This request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.