Provider registration actions should fire once or not at all when provider is inactive

[dpanta94]

🎫 Ticket

TCMN-178

🗒️ Description

Container would always fire registration actions of controllers for every time they would register and even if they were inactive.

As a result the following scenario would result in a fatal:

In ET -> Deactivate the main seating controller using a filter or const making the is_active method return false.
In ETP -> The main seating controller registers on the registration action of the ET's main seating controller.
We would have a fatal because the ET's main seating controller registration action would fire even when the controller is inactive.

🎥 Artifacts

Very low level change - making tests passing a valid artifact.

✔️ Checklist

• Ran npm run changelog to add changelog file(s). More info here
• Code is covered by NEW wpunit or integration tests.
• Code is covered by EXISTING wpunit or integration tests.
• Are all the required tests passing?
• Automated code review comments are addressed.
• Have you added Artifacts?
• Check the base branch for your PR.
• Add your PR to the project board for the release.