DSpace 7: type bind controlled fields are not cleaned once hidden

[steph-ieffam]

Describe the bug

When a submission form has a type bind controlled field there's an issue that occurs when the controlling field is switched to a different value and the restored to its previous value once again.
This behavior leads to a Patch request to be sent from the angular application towards the REST application.
The patch request fails due to an inconsistency in the data (the Angular application has not cleaned the data and considers the new data as a replacement for an old value but the REST application has cleared and removed all the non-allowed type bind field)

To Reproduce

Steps to reproduce the behavior:

1. configure type bind on dc.relation.journal for the value dc.type = article
2. start the submission and set dc.type = article
3. at this point dc.relation.journal is displayed
4. fill dc.relation.journal with any value
5. Save the submission
6. edit dc.type and set a different value
7. Save the submission
8. edit dc.type and select article once again
9. field dc.relation.journal is displayed
10. edit dc.relation.journal with a new value
11. Save the submission
12. An error occurs due to inconsistency in data between REST and Angular applications

Expected behavior

The submission fields should be cleared once hidden so that the same "cleanup" behavior implemented on the REST application is kept