Set debug ports to avoid port conflicts on 5005

[holly-cummins]

When running several quarkus apps, the logs complain about conflicts on port 5005. Us folks who us Quarkus all the time are used to it, and ignore it, but it can be worrying for new people. We should see if we can set ports in the services we scaffold to avoid the issue.

[holly-cummins]

This may be almost-solved for us. @maxandersen points out "Quarkus 3.5 enables automatic debugging on a random port when multiple Quarkus applications run in development mode. This allows you to easily debug a Quarkus app, regardless of the number of other apps running concurrently."

However, quarkusio/quarkus#33548 does still issue a warning if it has to choose a random port, so we're still generating a bit of log clutter and risking users getting worried about the warning. So on further thought I think we should still set something explicitly. The problem we're trying to solve isn't really "can I still attach a debugger when I have multiple apps," it's "can my app start cleanly without warning when I have multiple apps."

[maxandersen]

Is there something else we can print to not be problematic ?

It's atm a warning so you can more easily spot it over the default.

Like, the idea here is to not have to setup configuration to debug multiple apps.

[holly-cummins]

What about putting the output at info level? A warning is saying "there's something in your app configuration that you should go change to make this warning go away," whereas info would be "here's what you need to interact with this application."