feat(28664): Add schema management for the topic filters

[vanch3d]

See https://hivemq.kanbanize.com/ctrl_board/57/cards/28664/details/

This PR creates a new UX for managing the schema associated with topic filters. It refactors the secondary editor flow in the main list of topic filters (accessible through the "manage schema" CTA on every item).

The flow is based on three distinct operations:

• the "current schema", if already present, is displayed using the generic rendering paradigm. It is possible to remove it.
• a schema can be "uploaded" using a drag-and-drop interface or a file selector. The file is expected to be a JSON document, valid with JSON-Schema specification
• a schema can be "inferred" from the traffic on the current Edge instance. If matching topics exist, all their schemas are displayed, for one of them to be selected for replacing the current schema

The three operations are rendered in tabs on a dedicated side panel.

Out-of-scope

• JSON-Schema has a very relaxed validation process, to deal with a lot of cases. The properties are not even a mandatory part of the schema. The basic validation (RJSF + AJV) will only address structural errors (e.g. wrong JSON). Custom rules and restrictions on acceptable schemas should be considered.
• the uploaded schema is expected to be a data-url bundle (https://www.rfc-editor.org/rfc/rfc2397) and is stored as such with its topic filter. This assumption might have to be reassessed
• When uploading a schema, the file is directly updated on the relevant item in the list, by way of the PUT request. The GET cache is therefore updated and the React lifecycle automatically updates the DOM. The result is that the schema editor is closed abruptly. This behaviour might be considered too brusque for a proper UX and will be looked at in the subsequent ticket

Before

After