[docker] add missing settings to docker kibana.yml

[111andre111]

To https:/elastic/kibana/blob/master/src/dev/build/tasks/os_packages/docker_generator/resources/bin/kibana-docker

I checked against that an excel sheet manually generated
kibana-settings.xlsx

and the outcome were these settings missing in docker.

apm_oss.sourcemapIndices
cpu.cgroup.path.override
cpuacct.cgroup.path.override
csp.rules
csp.strict
csp.warnLegacyBrowsers
elasticsearch.ssl.alwaysPresentCertificate
interpreter.enableInVisualize
kibana.autocompleteTerminateAfter
kibana.autocompleteTimeout
logging.json
map.proxyElasticMapsServiceInMaps
map.regionmap
map.regionmap.includeElasticMapsService
map.regionmap.layers[].attribution
map.regionmap.layers[].fields[]
map.regionmap.layers[].fields[].description
map.regionmap.layers[].fields[].name
map.regionmap.layers[].name
map.regionmap.layers[].url
map.tilemap.options.attribution
map.tilemap.options.maxZoom
map.tilemap.options.minZoom
map.tilemap.options.subdomains
map.tilemap.url
newsfeed.enabled
server.compression.enabled
server.compression.referrerWhitelist
server.cors
server.cors.origin
server.keepaliveTimeout
server.socketTimeout
server.xsrf.disableProtection
telemetry.allowChangingOptInStatus
telemetry.optIn
telemetry.optInStatusUrl
telemetry.sendUsageFrom
xpack.apm.ui.transactionGroupBucketSize
xpack.graph.canEditDrillDownUrls
xpack.graph.savePolicy
xpack.license_management.enabled
xpack.monitoring.cluster_alerts.email_notifications.email_address
xpack.monitoring.elasticsearch.logFetchCount
xpack.reporting.capture.maxAttempts
xpack.rollup.enabled
xpack.searchprofiler.enabled
xpack.security.audit.enabled

Referring to issue
#39592
there were added lots of settings.
So now is the question:

1. Is there a way to generate a complete settings map against the source code because my manual approach may be not complete?

2. Should we still add these settings to docker entrypoint variables until this issue will be applied?
   Create plan to automate kibana-docker settings #30598

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[jbudz]

There isn't a high level way to aggregate between the new and old platform. I tried to hack something out a while back and was able to get all non deprecated settings, so it wasn't great.

Going forward the approach we want to take is to remove all snake case settings, and then remove that whitelist entirely. We'll be run a case change on everything.