feat!: Editable fields as JSON schema

[sbaudlr]

This PR has been opened by SuperFly.tv on behalf of EVS Broadcast Equipment (henceforth EVS).

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Feature (Closes #857).

What is the current behavior? (You can also link to an open issue here)

Editable fields use the deprecated config manifest format.

What is the new behavior (if this is a feature change)?

Editable fields now use JSON-schema.

Other information:

The ability to change the content of editable fields from the inspector in the shelf has been removed, as this is seemingly unused at the moment. It may be possible to use the components that have been developed for displaying JSON schemas in the config UIs for this purpose if desired, but this has not been tested.

Status

• Code documentation for the relevant parts in the code have been added/updated by the PR author
• The functionality has been tested by the PR author
• The functionality has been tested by NRK

[Julusian]

I think that this could do with some cleanup to be done too. This should mean that the ConfigManifestEntry and related types from blueprints-integration can be removed, as well as the ui components which draw them. I think that cleanup should be done in this PR, as this does make it all dead code.

I do not know enough about the inspector and potential usages of it to say whether it is ok to remove the editable fields section in the ui. But I think it would be better to leave the current ui bits in place, and to replace some of the inside of renderConfigFields with something like <span>Not implemented!</span>, so that when someone tries to use the editableFields property next they don't have to spend time trying to figure out why it isn't working and are instead reminded that it isnt implemented.

[sbaudlr]

I think that this could do with some cleanup to be done too. This should mean that the ConfigManifestEntry and related types from blueprints-integration can be removed, as well as the ui components which draw them. I think that cleanup should be done in this PR, as this does make it all dead code.

I do not know enough about the inspector and potential usages of it to say whether it is ok to remove the editable fields section in the ui. But I think it would be better to leave the current ui bits in place, and to replace some of the inside of renderConfigFields with something like <span>Not implemented!</span>, so that when someone tries to use the editableFields property next they don't have to spend time trying to figure out why it isn't working and are instead reminded that it isnt implemented.

I'll remove the unused things and look into doing something with the inspector next week.