Customize standard IJ Services view with Quarkus support

[angelozerr]

When auto create Quarkus run config #1233 will be implemented, the Services view will be filled automaticly with the Quarkus run config of imported project.

We need to custimize the Services tree to add some Quarkus support like:

• Open Dev UI
• Open started Quarkus application

like I have started with Quarkus Explorer #1233

The questions are:

• should we provide Quarkus support in Services view?
  • Pros:
    • It seems that it is the standard IJ means.
    • ex: Spring support from IJ has removed the custom Spring view to Services view
  • Cons:
    • Some kubernetes IJ user doesn't like this standard Servives view and prefer having a custom view
    • requires to create a Quarkus run config to fill the Services tree. We cannot display some runtime data like rest services, Quarkus build item without creating a run config. More those data are not linked to a run config but linked to a Quarkus project (ex : if you have several run config for the same project, we will duplicate those info on each run config tree item?)
    • My fear is that the Services tree can be hard to read since Services can host any run config (maven docker, etc)
• should we provide Quarkus support in a custom Quarkus Explorer view?
  • Pros:
    • user will see easily that there is a Quarkus view (on the right toolbar of the IJ) like it exists for Maven or Gradle project.
    • fill the tree with a lot of custom data like rest services, Quarkus builditem, Qute templates, etc
    • provide a Quarkus toolbar (ex : search rest services,Quarkus build item)
  • Cons:
    • Not the standard IJ means
    • Need to maintain the view (I see that since almost work hasbeen done for Quarkus explorer)

Perhaps I forget some Pros / Cons (and perhaps I'm not objective since I prefer having a Quarkus Explorer), @fbricon please update the issue with some Pros / Cons

@fbricon @ia3andy @gastaldi @adietish please give us your feedback, thanks!

[angelozerr]

Fixed with #1268 but IMHO I think we should have a Quarkus Explorer when we will need to add more features like rest services, Qute templates, etc in the tree view.