When component is deleted, ensure to remove all configuration for the deleted component

[framitdavid]

What: When a user deletes a component, we need to ensure that all configurations pointing to this component are appropriately removed across all files.

Relevant possible occurrences:

• in Expressions in all layout files
  • on layout level and
  • on component level
  • on boolean-fields
  • on textResources
  • in groups
• in componentRef in layouts (summary)
• in cells in rowsAfter(and other properties?) in RepeatingGroup
• in components/excludeFromPdf in all Settings files
• in ruleConfiguration and ruleHandler?

Backend: This issue can be resolved by implementing synchronization logic to handle the deletion of configurations distributed across multiple files in backend. Suggest that we implement this in the same way as we do with ProcessEditor task-id.

Frontend: The front end needs to add invalidation for all files specified in the SyncSuccess message received from the backend. We should rely on the backend to inform us about the changed files, and subsequently, we invalidate the cache accordingly. This issue entails implementing the necessary logic to invalidate cache entries based on the files specified in the SyncSuccess message from the backend.

### Acceptance criteria
- [ ] Users can delete components with configurations referenced in other files, and the system will clean up associated files.
- [ ] After deleting the component, users should observe an updated UI wherein all configurations related to the deleted component are removed.

### Playwrigth (e2e-tests)
- [ ] Add two different components to Page 1
- [ ] Configure component one to include an expression referencing component two.
- [ ] Delete component two
- [ ] Verify that the expression configuration referencing component two has been deleted.

[lassopicasso]

Related issue: https://github.com/Altinn/altinn-studio/issues/12564

[framitdavid]

Great work! Tested OK in dev. 👏