Overhaul the integration of the broker edition form within OpenShift

[lavocatt]

Very similar to #292 this issue has for objective to make sure that every button a user can click onto (except OLM) to edit a broker goes to our custom form.

Also in the search view:

How to proceed:

• Identify if a hook exists to support this use case, it might not be and if it isn't we might need to either rethink our approach or to come up with a clear usecase for the openshift console dynamic plugin folks and work conjointly with them to resolve that
• Use the hook that has been identified or has been implemented by the dynamic plugin sdk team.

[lavocatt]

There a few unknowns for this one, that's the reason I'm setting it to the M size. Maybe it'll work by default once #292 is done but it's too soon to be said.

[lavocatt]

One possible way to achieve this is to filter the Edit ActiveMQArtemis action using this extension:

And to add a new Edit Broker action using this extension:

It is unknown at this point if this strategy would work or not.

[lavocatt]

There's an issue with the current implementation. It allows for having the edition to show up correctly, but at the cost of entirely overloading the standard details page with the edition form:

When you click on the name of a broker there:

I'll open

Which is wrong, it shouldn't. We need to revert the PR that got merged 3 days ago, sorry about that @Msarawan

[Msarawan]

There's an issue with the current implementation. It allows for having the edition to show up correctly, but at the cost of entirely overloading the standard details page with the edition form:

When you click on the name of a broker there:

I'll open

Which is wrong, it shouldn't. We need to revert the PR that got merged 3 days ago, sorry about that @Msarawan

Thank you Thomas, for catching that! I had tested the edit-broker page functionality at both the search and installed operator instances. Last time, since the redirect wasn’t working as expected, I fixed it. and added custom edit-broker page by adding the url's in the console-extension file as recommended by the SDK team. It appeared to be resolved, but I hadn’t noticed the incorrect redirect when clicking on the names—thank you for identifying that oversight. I’ll work on fixing it now.