Add broker and trigger datamodel and visualization

[karthikjeeyar]

Fixes: https://issues.redhat.com/browse/ODC-4161

Analysis / Root cause:
Topology view doesn't support eventing brokers, triggers and its association with knative service

Solution:

1. Add data model to support broker and trigger
2. On broker visualization filter out the underlying base resources (InMemoryChannel) from the topology view
3. Add common actions in the sidebar and resource sections
4. Supports drag and drop from one service to another
5. Add create connector via the topology plugin
6. Add actions to channel/broker on context menu
7. Add kebab actions for Adding Trigger/subscription.
8. Hidden internal resources in the topology and showing it in sidebar.

Note: (Things are not covered part of this PR)

1. Add Trigger/ Add subscription actions will take the user to Add page in this PR (Opening Trigger modal will be handled in next PR)
2. Sidebar content rearrangement and enhancements will be on next PR.

Screenshots
kebab actions:

Broker context menu:

Trigger sidebar:

GIF:

Unit Test:

cc: @serenamarie125 @beaumorley @openshift/team-devconsole-ux @christianvogt

[invincibleJai]

@karthikjeeyar Thanks Verified locally , seems to work as expected with broker / trigger with and without filter's

• perpendicular line for trigger with filter was bit closer as per UXD. See if we can improve.
• on D&D of eventSourceConnector from a channel to broker, it says Move to Channel this should be as well dynamic i.e depending on channel or broker

[invincibleJai]

/lgtm

/assign @christianvogt

[christianvogt]

The event trigger marker is with a filter is incorrectly drawn as the filter indicator is way too far away from the circle. It moves depending on how far the two nodes are apart.

[christianvogt]

Channels and brokers aren't highlighting when moving a connector:

[karthikjeeyar]

@christianvogt @invincibleJai I have made the following changes

1. EventPubSubNode shape updated
2. Highlighting channels/brokers while moving the connector
3. Improved the perpendicular line for filter visualization, but still calculates the trigger line position based on the length of connector. (can we fix in later PR ?)

[karthikjeeyar]

/retest

[christianvogt]

@karthikjeeyar please create a new issue to address the trigger filter marker

/lgtm
/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt, invincibleJai, karthikjeeyar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [christianvogt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment