Feature: Data mapping extension + aligning reference lists

[madsrasmussen]

Build on top of #18311 - Review this first

This PR implements a fully dynamic approach to listing references in a document/media workspace supporting the polymorphic response from the server.

Until now, the reference lists have had a hardcoded solution with support for document, media, and member entities. With this PR, we use the entityRefItem extension to render a reference based on the entity type in the data.

The reference endpoint returns a "mixed" response, which can consist of multiple entity types. The endpoint doesn't specify the entity type of an entry but only the type of the response model. To prevent a hardcoded solution, the PR introduces a dataMapping extension that can map any data based on an identifier in the data.

Manifest:

 {
  type: 'dataMapping',
  alias: 'Umb.DataMapping.ManagementApi.DocumentReferenceResponse',
  name: 'Document Reference Response Management Api Data Mapping',
  api: () => import('./document-reference-response-model.mapper.js'),
  dataSourceIdentifier: 'Umb.ManagementApi',
  dataModelIdentifier: 'DocumentReferenceResponseModel',
 },

Example:

export class UmbDocumentReferenceResponseManagementApiDataMapping
  extends UmbControllerBase
  implements UmbDataMapping<DocumentReferenceResponseModel, UmbDocumentReferenceModel> {

  async map(data: DocumentReferenceResponseModel): Promise<UmbDocumentReferenceModel> {
    return {
      // map data here
    };
  }
}

export { UmbDocumentReferenceResponseManagementApiDataMapping as api };

[nielslyngsoe]

@madsrasmussen I just have one thing that I like you to consider and then I'm happy, I have read all the code and tested the various cases.