fix: registration data cache invalidation

[aberonni]

AB#33731

This makes sure that we invalidate cache for registration queries that rely on referenceId, as well as the queries that rely on registration.id

This was causing issues because the new "getDuplicates" endpoint (implemented in #6522) uses referenceId, and the cache for it was not being invalidated after editing personal information.

Checklist before requesting a review

• I have performed a self-review of my code
• I have added tests wherever relevant
• I have made sure that all automated checks pass before requesting a review
• I do not need any deviation from our PR guidelines

Portalicious preview deployment

https://lively-river-04adce503-6530.westeurope.5.azurestaticapps.net

Copilot reviewed 5 out of 7 changed files in this pull request and generated no comments.

Files not reviewed (2)

• interfaces/Portalicious/src/app/pages/project-registration-personal-information/project-registration-personal-information.page.html: Language not supported
• interfaces/Portalicious/src/app/pages/project-registrations/components/import-registrations/import-registrations.component.ts: Evaluated as low risk

Comments suppressed due to low confidence (1)

interfaces/Portalicious/src/app/domains/registration/registration.api.service.ts:308

• Ensure that the 'registration' parameter is always an instance of 'Registration' before accessing its properties.

await Promise.all([