Update CORS configuration

[dennisvang]

Replaces legacy CORSFilter implementation by modern configuration based on CorsRegistry.

This uses the same CORS settings as the original implementation, viz. allow all origins.

I did not check if it is desirable and/or safe to keep those settings. May be a good idea to review that choice.

fixes #549

[MarekSuchanek]

@dennisvang could you please rebase based on the updated develop where dependencies were updated (so it should also pass the security checks) and check it still works as desired?

Also, are you OK to switch from bugfix to chore? Or it was not working properly before the change?

[dennisvang]

@dennisvang could you please rebase based on the updated develop where dependencies were updated (so it should also pass the security checks) and check it still works as desired?

Hi @MarekSuchanek thanks for picking this up. I'll rebase a.s.a.p.

Also, are you OK to switch from bugfix to chore? Or it was not working properly before the change?

The change was prompted by #549 so I guess bugfix would apply.

[dennisvang]

@MarekSuchanek The Snyk Maven check keeps failing to authenticate, for some unknown reason. The PR does not change anything related to github actions. Any ideas?