feat(29319): Add notification of not writable config

[vanch3d]

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

The PR adds a notification when the config-writeable capability is NOT defined

Out-of-scope

• Capabilities MUST be curated in the OpenAPI specs, not replicated on the front end. This will be part of a further ticket
• The intended usage of the capability has been inverted. The critical aspect worth notifying users about is when the config is NOT writable, triggering error messages (403) at the front end. However, that state is (mis)detected by the capability (config is writable) being not present in the capabilities list. The undefined content could mean not supported but also not found or API to get the capabilities failed. As the logician says: "Absence of Evidence does not mean Evidence of Absence”. This will be fixed in a further update

After

[h2xd]

LGTM! 🐊