[Security solution][Endpoint] Remove unnecessary experimental feature flags from plugin config

[paul-tavares]

Summary

• Changes the behaviour of the validation of xpack.securitySolution.enableExperimental values (defined in the kibana.yml) so that unknown/unsupported values will no longer prevent the application from starting (will no longer throw)
  • This change is only done in the config schema validation
  • Plugin's setup will now output a message (warning) to the log if it finds experimental feature values that are not supported.
• Removes the following experimental feature flags (no longer needed):
  • policyListEnabled
  • diableIsolationUIPendingStatuses
  • responseActionsConsoleEnabled
  • endpointRbacEnabled
  • endpointRbacV1Enabled
  • responseActionGetFileEnabled
  • responseActionExecuteEnabled
  • pendingActionResponsesWithAck
  • policyResponseInFleetEnabled
  • riskyUsersEnabled
  • riskyHostsEnabled

---

Message to kibana log when unsupported values are defined:

[2023-06-02T16:37:48.997-04:00][WARN ][plugins.securitySolution.config] Unsupported "xpack.securitySolution.enableExperimental" values detected.
The following configuration values are no longer supported and should be removed from the kibana configuration file:

    xpack.securitySolution.enableExperimental:
      - endpointRbacEnabled
      - responseActionGetFileEnabled
      - responseActionExecuteEnabled

[machadoum]

Thanks for this improvement!

Feel free to delete this code:

/**
   * Keep DEPRECATED experimental flags that are documented to prevent failed upgrades.
   * https://www.elastic.co/guide/en/security/current/user-risk-score.html
   * https://www.elastic.co/guide/en/security/current/host-risk-score.html
   *
   * Issue: https://github.com/elastic/kibana/issues/146777
   */
  riskyHostsEnabled: false, // DEPRECATED
  riskyUsersEnabled: false, // DEPRECATED

[elasticmachine]

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

[joeypoon]

me: reads PR title, oh this should be easy
PR: 40 file changes
🤣

thanks for the cleanup 🔥

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 7bdd739

Failed CI Steps

• Investigations - Security Solution Tests #1

Test Failures

• [job] [logs] Investigations - Security Solution Tests #1 / Detections : Page Filters Alert Page Filters Customization should not sync to the URL in edit mode but only in view mode

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	4105	4103	-2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	10.8MB	10.8MB	-2.1KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
securitySolution	51.4KB	51.0KB	-356.0B

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	19	21	+2
securitySolution	413	418	+5
total			+7

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
securitySolution	497	502	+5
total			+7

History

• 💛 Build #132645 was flaky 5d26ed1
• 💔 Build #132623 failed 574e48e
• 💔 Build #132299 failed 3dd0e0a
• 💔 Build #132292 failed 24725f3

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

cc @paul-tavares

[machadoum]

The explore code looks good to me.
I noticed that riskyUsersEnabled and riskyHostsEnabled are still present in the branch.