feat: convert remote-console service to Fabrica

[cjh1]

Checklist

• My code follows the style guidelines of this project
• I have added/updated comments where needed
• I have added tests that prove my fix is effective or my feature works
• I have run make test (or equivalent) locally and all tests pass
• DCO Sign-off: All commits are signed off (git commit -s) with my real name and email
• REUSE Compliance:
  • Each new/modified source file has SPDX copyright and license headers
  • Any non-commentable files include a <filename>.license sidecar
  • All referenced licenses are present in the LICENSES/ directory

Description

This is an experiment to rework the remote-console service to use Fabrica.

remote-console is not a standard CRUD application, so it does not fit the default Fabrica workflow cleanly. This PR is paired with a Fabrica fork that adds the changes needed to make Fabrica useful for this service, including:

• configuring resource paths and operations in apis.yaml
• filtering generated handlers, routes, clients, OpenAPI, CLI, and AuthZ output
• adding persistence hooks for storage-independent handlers

Fabrica branch:

https://github.com/cjh1/fabrica/tree/remote-console

The idea is that even though remote-console does not use Fabrica’s storage backend, Fabrica may still provide value through versioning, AuthN, AuthZ, events, and consistency with other OpenCHAMI services.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update