chore(ci): improve PR, Issues, and release automations

[dreamorosi]

Description of your changes

This housekeeping PR introduces a number of changes related to automating issues and PRs:

• configures boring-cyborg to add area/* labels to a PRs based on the path of the files that have changed
• tweaks the configuration of the automation that adds type/* labels to PRs based on the title
• adds scopes to semantic title validation (i.e. feat(logger) -> logger is a scope)
• improves the regular expression that checks the issue number in the PR body to include closing keywords
• improves the automation that labels issues linked to a PR being closed so that it removes any status/* label while adding the status/pending-release one
• adds a new automation that upon release, will query all closed issues with status/pending-release and label them as status/complete as well as leaving a comment that informs about the release

Finally, it also streamlines the PR template by removing some redundant fields and checklist items.

Once merged this PR closes #133

Related issues, RFCs

Issue number: #133

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding changes to the examples
• My changes generate no new warnings
• The code coverage hasn't decreased
• I have added tests that prove my change is effective and works
• New and existing unit tests pass locally and in Github Actions
• Any dependent changes have been merged and published
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.