After a migration, the IDP checkbox Allow CRUD operation is not shown as enabled in the UI (but is enabled in the backend)

[exalate-issue-sync]

To reproduce:

• Use an AM instance that doesn’t include this feature [identity providers] Prevent CRUD operation on Mongo and JDBC IDPS #8695 (as a reference, it has been included in 3.15.15, 3.18.13, 3.19.4, 3.20.0 and 3.21.0)
• create a new IDP mongo
• via AM, create a new user that belongs to the new mongo IDP
• Upgrade to an AM version that includes the CRUD operation feature
• Go to the mongo IDP in the UI and the Allow CRUD operation checkbox is not checked
• Go to the created user and modify its password

This probes that the functionality is enabled by default, but this is not reflected in the UI.

Below a small gif I captured after doing the configuration in 3.19.3 and migrated to 3.19.4

[exalate-issue-sync]

This issue has been fixed in versions 3.21.7, 3.20.12, 4.0.2, 4.1.0, 3.19.18