Fix Data Integrity Issues once Integrity Checker solves conflicts for Roles.

[joseorsini]

If a CMS Tab/Tool depends on an user-created role, the Integrity Checker does not update references on environments and process fail because of enforced Data integrity objects in DB side (foreign Keys).

Scenario is:

1. Create a role on separate environments, using the same role name and key.
2. Create a custom tab for it and assign different tools for it.
3. Run the integrity checker. A conflict between roles is found.
4. Whether a local or remote fix is triggered, it fails because the layouts_cms_roles table enforces data integrity with cms_role table. Once the new role is recreated on the DB, old one is dropped but existing references between it and CMS Tabs are not properly updated.

[joseorsini]

PR: #13068

[bryanboza]

Fixed, tested on the last master // Postgres // Chrome

[joseorsini]

Please include this one for 4.3.3 release.
Requested by customer: https://dotcms.zendesk.com/agent/tickets/95565