[Issue] Prune triggers after setting database up properly

[m2-assistant]

This issue is automatically created based on existing pull request: #33092: Prune triggers after setting database up properly

---

Description

When installing a new module which both installs tables and associated mview indexers, Magento fails to run setup:upgrade successfully.

This is because there is a step within setup:upgrade that's designed to prune old triggers from the database that happens before the new database state is established. The implementation detail of this prune is: remove all the known-good triggers, remove all other triggers, reinstate known-good triggers. It's the last step here that's causing issue. When this step tries to reinstate the "known-good" triggers, it's using the new code and therefore needs the new tables that haven't yet been created.

This pull request is a work-around for the problem described here. A proper fix would be to avoid unsubscribe/resubscribe of triggers within this prune step entirely.

Related Pull Requests

none

Fixed Issues

• Fixes Error during installation on Magento >=2.4.1 Smile-SA/elasticsuite#2130

Manual testing scenarios

1. Install Magento
2. Set indexers to "Update by Schedule": php bin/magento indexer:set-mode schedule
3. Add bug33092.tar.gz with tar xzf bug33092.tar.gz
4. Enable the module with php bin/magento module:enable Magento_Bug33092
5. Run php bin/magento setup:upgrade
6. Witness error message / lack of error

Questions or comments

None

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)

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-8381 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.