feat(19709): Add tablular visualisation of policies, scripts and schemas

[vanch3d]

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

The PR refactors the main Data Hub landing page to offer access to a table-based visualisation of all the policies and their resources, scripts and schema, present in the Edge.

The lists are displayed in separate tabs on the UI and are paginated, as with previous table usages. Filtering is not yet supported.

The policy table offers a principal CTA to create new ones. Similar features are not available for the scripts and schemas (their creation should be handled as part of the policy creation by the Designer).

The actions on each line of the tables offer deleting the items. An edit button is offered for the policy but not for the resources (again, editing resources is assumed to be handled by the designer)

Out-of-scope

• safeguards and feedback on deletion will be done in a subsequent ticket, see https://hivemq.kanbanize.com/ctrl_board/57/cards/19819/details/

Before

After

[sfrehse]

How are these items currently ordered?

[vanch3d]

As with all the tables, items are not initially sorted in any way. They are displayed as they are produced by the backend. Then all the actionable fields (i.e. all except "Actions") can be used to sort the columns. Don't forget to try the SHIFT+click to do multiple sort conditions.

[ryanbateman]

A question about the text "Your transformation code will be listed there" in the UI (and equivalents in other screens) - I think (if I understand what this is trying to say) that this writing could be phrased to sound a little more natural. It reads (quite understandably) like non-native English. What's the current process for defining and feedback for this kind of UX writing?

[vanch3d]

A question about the text "Your transformation code will be listed there" in the UI (and equivalents in other screens) - I think (if I understand what this is trying to say) that this writing could be phrased to sound a little more natural. It reads (quite understandably) like non-native English. What's the current process for defining and feedback for this kind of UX writing?

At the moment, it's mostly a bespoke process. We fix typos and wording when we spot them through usage or review.

All the strings are externalised as part of the internationalisation process (see https://github.com/hivemq/hivemq-edge/blob/master/hivemq-edge/src/frontend/src/locales/en/components.json for example). The translation format is one of the standards used by the CAT industry and should be integrated easily for review (see https://poeditor.com/ for a good example). Even if we don't support localisation yet (but, after all, US-English is a translation ;-) )