What you describe is very strange.
If someone changes a shared module, and some tests fail in result, his changes simply should not be merged.
> you will get a ticket to understand what has changed, make changes and fire up every tests
Do you fire tests manually?
It works well enough if everything is making money and is being actively developed.
There is substantial tooling assistance to assist with this, and it's common to make changes by adding new functionality, writing an automated transform to shift usage from old to new, sharding out the reviews to the suitable OWNERS, and finally removing the old functionality.
Very heavily used common code tends to be owned by teams that are used to this burden. That said, it does complicate upgrades to third party components.