Changing entity type of PublicFormConfig breaks the configured fields

[sleidig]

          @sleidig @Abhinegi2 In the (child/school/notes)entity, "edit data structure," where the list of all public forms is available, the entity field should be non-editable. 

Keeping the entity field editable, messes up the configuration of the field in public forms. What do you think?

Originally posted by @george-neha in #2708 (comment)

[Abhinegi2]

@sleidig and @george-neha Below are a few suggestions that come to my mind, go through these and let me know which one looks good and if you have any other approach/suggestion also let me know

1 Disable Entity Type After Creation

• When creating a new Public Form (PF), display an explanation near the entity type selection field:
  "Once the Public form is created/saved, you cannot change the entity type later."
• After saving, the entity type field becomes disabled in edit mode.
• If a user wants to change the entity type later, they would need to delete the form and create a new one from scratch. This involves re-entering details like the title, description, logo, fields, and prefilled values.
  (it can be a time-consuming process for users)

2 Allow Changing Entity Type with Confirmation dialog

• Allow users to change the entity type even after saving.
• Display a confirmation dialog/popup when the user changes an entity type:
  "Are you sure you want to change the entity type? This action will remove all existing fields, and you will need to add new fields specific to the new entity type."
• If the user confirms, the system removes the current fields, and the user needs to add fields for the new entity type.
  (focuses on user convenience with clear warnings about the implications of changing the entity type)

[sleidig]

As discussed in the team, we'll go for making the "entity" type selection field read-only after it has been initially set.

@Abhinegi2 , I am not sure how you can best implement that within our EntityForm framework ... Maybe we could implement a "Validator" (similar to uniqueIdValidator) that both invalidates any changes and also, as a side effect, disables the FormControl?

[Abhinegi2]

Thanks for the suggestion, I’ll proceed with the following:

• Add a new "readonlyValidator" component similar to the existing uniqueIdValidator.
• Integrate "readonlyValidator" into the DynamicValidatorsService, so it can be applied dynamically to form controls within the EntityForm framework.
• Update the EntityForm logic to integrate the readonlyValidator for the entity type fields.

[Abhinegi2]

@george-neha, could you please test the following on the: https://pr-2815.aam-digital.net/

• Verify that the Entity Type field becomes disabled/read-only after a value is set.
• Similarly, ensure that the Name and Center fields are disabled/read-only once their initial values are set in the Child entity.

[george-neha]

@Abhinegi2 Can you grey out the Entity/Name/Centre field to give the impression that the fields are non-editable?

[Abhinegi2]

@george-neha implemented the suggestion have a look now on the: https://pr-2815.aam-digital.net/