Invalidate cache for updated files in Process

[lassopicasso]

Description of the bug

When editing the taskId for a task, the application continues to use the old taskId from layoutsets until the page is refreshed. This behavior indicates that the cache is not being invalidated correctly when updates occur.

To handle this issue, and similar cases in the future, we need to ensure that the cache of the updated files is invalidated properly. This can be achieved by leveraging the WebSocket message handling mechanism.

When a message is received from the backend in the onWSMessageReceived function and it indicates success, the message.source brings info about the updated file(s).

Using the information from message.source, we can map the updated file to the corresponding query keys that should be invalidated. This ensures that the cache reflects the latest state of the data.

Steps To Reproduce

1. Go to process page
2. Add 2 layoutsets
3. Update the task id for one of them
4. Go to the other layoutset and update with same task id as the other one. (no error message, because it still checks the old taskId)

Additional Information

No response

[framitdavid]

Tested OK in dev.