Fix RestAssured URL handling and unexpected restarts in QuarkusProdModeTest

[famod]

This is fixing an issue we had over at quarkiverse/quarkus-cxf#669 (comment) (cc @shumonsharif @ppalaga).

Without this fix QuarkusProdModeTest does the following when run and expectExit are enabled:

• beforeAll:
  • start the app and wait for it to exit
  • setup RestAssured URL (RestAssuredURLManager stores the previous port)
• beforeEach :
  • again start the app and wait for it to exit
  • again setup RestAssured URL, loosing the initially stored port to restore
• afterAll:
  • clear the RestAssured URL, but not with the initially stored port

This fix:

• makes sure that the app is not stared again for each test method when expectExit is enabled
• does not even set up RestAssured URL when expectExit is enabled (App will have exited anyway)
• make setup/clean of RestAssured URL consistent with (manual) start()/stop()

Please note that there can still be inconsistencies w.r.t. to the URL when using multiple QuarkusProdModeTests because there is only one static URL Manager, not one for each extension.

[geoand]

LGTM

[Sgitario]

lgtm

[quarkus-bot]

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[ppalaga]

@gsmet could we please get this backported to 2.13?

[gsmet]

I added the label and we will discuss it with @rsvoboda when we work on the next 2.13.