align cors settings names with elasticsearch

[mshustov]

Summary

#84316 introduced CORS support with settings:

server.cors.enabled: boolean
server.cors.credentials: boolean;
server.cors.origin: '*' | string[];

however Elasticsearch uses a bit different naming schema:

server.cors.enabled: boolean
server.cors.allow-credentials: boolean;
server.cors.allow-origin:  string[];

See https://github.com/elastic/elasticsearch/blob/f8c013d0fbb4ac55141891a56282f8b636aea62c/docs/reference/modules/http.asciidoc

• We should align the naming across the stack.
  Note: we don't use the kebab-case naming schema for the settings.
  Based on this comment [Discuss] API naming convention #52284 (comment) I'm renaming server.cors.credentials to server.cors.allowCredentials; server.cors.origin to server.cors.allowOrigin.
  I'd expect we rename (to use snake_case) the settings in both Kibana and Elasticsearch during Settings should use snake_case #7444

• we should align schema across the stack. server.cors.allowOrigin: '*' is refactored to be server.cors.allowOrigin: ["*"]

Plugin API changes

I'm going to update the docs in #84316

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: c764de2

Metrics [docs]

Distributable file count

id	before	after	diff
default	47129	47889	+760

History

• 💚 Build #93910 succeeded 30441a5

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream