Do not reapply patches in case it got already applied with one of it's aliases

[aschrammel]

Description (*)

In case a patch has defined aliases in getAliases it should be checked, if one of those aliases already got applied before and is fixed in patch_list DB table.
In case it is, the patch must not be reapplied as it just got renamed / moved for some reason, but we still want to make sure the new name is also fixed in patch_list DB table.

Related Pull Requests

1. [Fixed: #31396] Data/Schema Patches getAliases() not working as expected #31635

Fixed Issues (if relevant)

1. Fixes [Magento 2.3.x] Declarative Schema :: Data/Schema Patches getAliases() not working as expected #23031
2. Fixes [Magento 2.3.x] Data/Schema Patches getAliases() causes errors during setup:upgrade #31396

Manual testing scenarios (*)

1. Create a data and a schema patch
2. Apply the patches by running bin/magento setup:upgrade
3. Create a new data and schema patch having the respective patches from above defined in getAliases
4. Apply the patches by running bin/magento setup:upgrade
5. Verify that the new patches weren't re-applied but fixed in the patch_list DB table

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @aschrammel. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.