Do not support any Origin by default if CORS is enabled

[sberyozkin]

If CORS is enabled then the users have to take an action and enable the wildcard if they really need to, as opposed to Quarkus doing it by default. This update will hopefully encourage users take CORS configuration more seriously.
DevUI is not expected to be affected.

Note I'm adding the wildcard to the tests to have them passing again, which also shows that the users who need a wildcard will only have to add one more property.
The migration guide update will follow.

[sberyozkin]

Sorry, will clean it up, I thought I knew which tests could be affected

[maxandersen]

+1 on the principle here; Enabling CORS should not have * by default given we apply #29626 so same origin still works.

Would prefer if @stuartwdouglas or @cescoffier verifies the implementation beyond just me.

[sberyozkin]

Thanks @maxandersen, sure, as commented in the other issue, Stuart's same origin check fix is a better version of * for such a check. But yes, let Stuart/Clement double check, rebasing this PR now

[quarkus-bot]

Failing Jobs - Building e85bea0

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 MacOS M1	Set up runner	⚠️ Check →	Logs	Raw logs
✔️	JVM Tests - JDK 18

Boolean all origins value is introduced as requested

[sberyozkin]

Hi @stuartwdouglas I'll go ahead with the merge tomorrow if you don't have other comments, thanks

[sberyozkin]

Migration guide has been updated: https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.16#no-wildcard-origin-support-by-default-for-cors-filter