Unauthorized route migration for routes owned by kibana-management

[kibanamachine]

Authz API migration for unauthorized routes

This PR migrates unauthorized routes owned by your team to a new security configuration.
Please refer to the documentation for more information: Authorization API

Before migration:

router.get({
  path: '/api/path',
  ...
}, handler);

After migration:

router.get({
  path: '/api/path',
  security: {
    authz: {
      enabled: false,
      reason: 'This route is opted out from authorization because ...',
    },
  },
  ...
}, handler);

What to do next?

1. Review the changes in this PR.
2. Elaborate on the reasoning to opt-out of authorization.
3. Routes without a compelling reason to opt-out of authorization should plan to introduce them as soon as possible.
4. You might need to update your tests to reflect the new security configuration:

• If you have snapshot tests that include the route definition.

Any questions?

If you have any questions or need help with API authorization, please reach out to the @elastic/kibana-security team.

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 64728f4

Metrics [docs]

✅ unchanged