Webcomponents can be configured within the prefs.xml

[Diginaut]

Description, Context and related Issue

This change adds the ability to configure web-components directly within the prefs.xml file. Web-components can now be defined with key-value option pairs, allowing for flexible and centralized configuration management.

Changes Made:

1. edirom-prefs.xml: Added a commented example demonstrating how web-components can be configured (e.g., edirom_keycloak_handler with URL, realm, client ID, and script path)
2. getPreferences.xql: Enhanced the preferences retrieval logic to parse and return web-component configurations along with their options as a structured map

This enables applications to:

• Dynamically load and configure web-components through the preferences system
• Support multiple web-components with their individual settings

Closes #165

How Has This Been Tested?

• With and without custom prefs.xml
• With and without web-components entry in prefs.xml

Types of changes

• New feature (non-breaking change which adds functionality)
• Improvement

Overview

• I have updated the inline documentation accordingly.
• I have performed a self-review of my code, according to the style guide
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes at testing
• All new and existing tests passed.

[daniel-jettka]

Hi @Diginaut Sorry I won't find time to review this. Can you please assign someone else?