[Fleet] Fix creating a policy in a different space than the current

[nchaulet]

Summary

Resolve #203527

Fix creating a policy in a different space than the current one.

Tests

I added automated API integration test to cover that scenario.

You can manually test this by enabling space awarenes (feature flag + API call)

with 2 space (default and test)

Create a policy in test from the default space, verify that policy is only visible in the test space.

In default space:

In test space:

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[nchaulet]

@elasticmachine merge upstream

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 3005542

Failed CI Steps

• Fleet Cypress Tests #2
• Fleet Cypress Tests #2
• Fleet Cypress Tests #4
• Fleet Cypress Tests #4

Test Failures

• [job] [logs] Fleet Cypress Tests #4 / Add Integration - Automatic Import should create an integration
• [job] [logs] Fleet Cypress Tests #4 / Add Integration - Automatic Import should create an integration
• [job] [logs] Fleet Cypress Tests #2 / When the user has All permissions for Integrations and All permissions for actions Create Assistant is not accessible but upload is accessible
• [job] [logs] Fleet Cypress Tests #2 / When the user has All permissions for Integrations and All permissions for actions Create Assistant is not accessible but upload is accessible

Metrics [docs]

Async chunks

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

id	before	after	diff
fleet	1.7MB	1.7MB	+3.0B

History

• 💔 Build #265304 failed 367c783
• 💔 Build #265251 failed 1901a6b

cc @nchaulet