fix(event-handler): fixed CORS behaviour not aligned with CORS spec

[sdangol]

Summary

This PR fixes some of the bugs that were introduced in the CORS middleware

Changes

Please provide a summary of what's being changed

• Fixed issue with wildcard origins when included in array
• Removed resolveOrigin function and made it inline
• Added logic to check for requested method to match with allowed method in preflight request
• Added logic to check for requested header to match with allowed headers in preflight request
• Refactored some of the tests

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: closes #4509

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[dreamorosi]

@sdangol can you try to simplify the function a bit further? SonarCloud is reporting a higher than normal complexity.

I see that there are two instances where we check isOptions, I wonder if we can merge them into one and return the NO_CONTENT response early by rearranging or slightly repeating things. This would probably bring the cognitive complexity down.

Alternatively, even though in previous iterations we consolidated everything in its body, now that it has grown maybe we do need to split some parts.

[dreamorosi]

Quality Gate passed

Issues 1 New issue 0 Accepted issues

Measures 0 Security Hotspots 0.0% Coverage on New Code 0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Almost there :D

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud