[WIP] Use ogc-client for WMTS rendering

[jahow]

Description

This PR uses the WMTS support from ogc-client to offload the WMTS parsing logic to the library.

Architectural changes

none

Screenshots

[...]

Quality Assurance Checklist

• Commit history is devoid of any merge commits and readable to facilitate reviews
• If new logic ⚙️ is introduced: unit tests were added
• If new user stories 🤏 are introduced: E2E tests were added
• If new UI components 🕹️ are introduced: corresponding stories in Storybook were created
• If breaking changes 🪚 are introduced: add the breaking change label
• If bugs 🐞 are fixed: add the backport <release branch> label
• The documentation website 📚 has received the love it deserves

[github-actions]

Affected libs: feature-map, feature-dataviz, feature-record, feature-router, api-metadata-converter, api-repository, feature-catalog, feature-search, feature-auth, feature-editor, ui-search, data-access-datafeeder, util-data-fetcher, util-app-config, common-fixtures, util-shared, ui-elements, ui-catalog, ui-widgets, ui-inputs, ui-layout, ui-map, data-access-gn4, common-domain, ui-dataviz, util-i18n,
Affected apps: metadata-editor, datahub, demo, webcomponents, search, map-viewer, datafeeder, metadata-converter, data-platform,

• 🚀 Build and deploy storybook and demo on GitHub Pages
• 📦 Build and push affected docker images

[jahow]

@fgravin what do you think of this? This would offload a lot of responsibility to the library.

[github-actions]

📷 Screenshots are here!