Apply type hierarchy resolution to resources

**Motivation**
Following #4663 about introducing a new entity to define and manage type hierarchy resolution, the next step is to apply it to resources during creations and updates

**Acceptance criteria**
1. When a user creates or updates a resource, the provided types are enriched with their hierarchy types.
2. If no mapping are found for a type, the type is kept.
3. A new field is introduced to keep track of the original types so that we can recompute the list of types if needed
4. The original types are returned as metadata when fetching the resource
5. The source has to remain what the user has provided

**Not in scope**
1. Update the type hierarchy during refreshes