fix #10505 Allow to specify use of proxy or cors at layer level

[rowheat02]

Description

• fixes Allow to specify use of proxy or cors at layer level #10505. proxy by default implemented if any endpoint fails due to CORS
• UI removed for: Force proxy (Layer Settings) and the Allow not secure layers
• Interceptor has been used to use retry with proxy to all Axios endpoints.
• For Cesium, before adding a layer to the map one preflight request is used to check CORS and use the proxy.
• Common proxy cache for both cases.

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring
• Build related changes
• CI related changes
• Other... Please describe:

Issue

What is the current behavior?

#10505

What is the new behavior?
AutoProxy for CORS disabled endpoints.

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

[rowheat02]

• UI removed for: Force proxy (Layer Settings) and the Allow not secure layers
• If any api fails due to CORS, proxy will be used by default in ajax interceptor.
• In case of cesium, preflight CORS check api will be called before adding layer and forceProxy option will be used to create new layer which handle proxy logic in layers.
• common proxy cache logic implemented.
• Old Failed test cases other than "should create a bil terrain provider with wms config" have been solved. In this last failed test, two async parts are there throwing timeout error.