…ult view handler

URLs that start with /faces/* are handled by xhtml pages
(e.g. /faces/header.xhtml handled by header.xhtml (in the webapp root).
Can be injected to JSF templating pages via iframe.
Example in upload.jsf (Application -> Deploy...)

Adds a custom resource handler wrapper that loads facelets from a console plugin, from the META-INF/resources directory.
Adds a Console plugin for command recorder, which provides a menu facelet wtih a toggle button. The MenuView bean is not found yet.

Button to toggle Command logger
Simplified plugins via Faces - plain JARs in Admin WAR,
which contain facelets and resources in META-INF/resources,
and Java model as plain CDI beans in the JAR.

Subject is retrieved from Jakarta Security - worth to move to a common module.

…ommandrecorder plugin

Moved all the code needed to integrate the Command Recorder console plugin into the plugin module. This means that Admin Console will work without issues if the module is not present.

Since the Admin Recorder plugin is deployed in the AdminGUI application and not as an OSGi bundle in modules, I needed to update the ConsolePluginService:

* it's now created by an HK2 locator specific to the deployed app, so that it finds console plugins also in the web app, not only in OSGi modules
* it searches for all plugin configuration files in the classloader and remove duplicities (because the web app classloader also finds all files in OSGi bundles via the parent classloader)

Also removed the demo facelets files.(header.xhtml, etc.)

Moved CDI producers into Admin Core, so that they can be reused by other modules and we avoid conflicts or implicit dependencies if multiple modules define the same producers or rely on beans produced by other modules.

Removed unnecessary Serializable