🐛 Change CORS layer construction to allow wildcard

[JMicheli]

This pull request addresses the problem raised in #537, which causes Stump to fail to start when a wildcard ("*") is used in the allowed origins configuration variable.

The cause is that Axum doesn't like wildcards being added via the AllowOrigin::list() function and wants you to use AllowOrigin::any() instead. I slightly reorganized the server's get_cors_layer() function to detect when a "*" is present in the list of allowed origins and exit early with an AllowOrigin::any() configuration.

I'm making the assumption is that there is no case where the allowed origin list would include a wildcard and then other origins but the user would expect behavior other than any origin being allowed. I think that's right.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 35 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
apps/server/src/config/cors.rs	0.00%	35 Missing ⚠️

Files with missing lines	Coverage Δ
apps/server/src/config/cors.rs	0.00% <0.00%> (ø)

... and 4 files with indirect coverage changes

[aaronleopold]

This looks great, thank you!!

I'm making the assumption is that there is no case where the allowed origin list would include a wildcard and then other origins but the user would expect behavior other than any origin being allowed. I think that's right.

Yeah I think this is the correct assumption, it doesn't make sense to say "I want any origin, but also this specific one" since it would be covered by the wildcard