enhancement: console integration

[fschade]

Description

Introduce a new console service that integrates the system with the console remote (instance management). It establishes the foundation for remote-driven functionality across the platform.

As a first use case, theme management is now handled via the remote service.

Motivation and Context

Introduce a console service to integrate the remote console service.

Changes

Console Service (main focus)

• Introduced a new console service as an integration layer
• Connects the system with the console remote (instance management)
• Provides the foundation for remote-managed features

Web-Theming (first use case)

• Replaced static themes with runtime-managed themes (for console themes only)
• Uses shared storage to support distributed environments
• Integrated with console remote to consume managed themes

SSE

• Added support for subscribing to multiple topics (such as, all-users: theme updated notification)
• Replaced previous SSE library (single-topic limitation)

How to test it

• get and bootstrap the remote console service
• remote console service: create an instance
• opencloud: copy the instance token and make it available CONSOLE_REMOTE_JWT_TOKEN=xxx
• opencloud: enable the console integration START_ADDITIONAL_SERVICES="console"
• opencloud: start the server as usual
• opencloud cli - subscription based: oc console update subscribe
• opencloud cli - cmd based: oc console update run web-theme-get
• opencloud web ui: reaload the ui

Open Questions

• is the cs3 system storage needed? or should we use the fs (needs writable storage)
• should the theme data live in the web space or in the context of the console service
• events.SendSSE uses UserIDs for the toic, since the pr introduces the ability to subscribe to multiple topics, is it still a good naming?

ToDos

• !!! VIP !!! release build flag (tls insecure)

Related topics

• https://github.com/opencloud-eu/console
• https://github.com/opencloud-eu/console/pull/228
• https://github.com/opencloud-eu/console/issues/73

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

[fschade]

@AlexAndBear, please add your feedback regarding multi topic sse notifications :) a web draft is already done... but i wanna get your feedback first.

[sonarqubecloud]

Quality Gate failed

Failed conditions
6.8% Duplication on New Code (required ≤ 3%)
D Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE