[Fleet] Fix migration 7.12 to 7.13 migrate settings

[nchaulet]

Summary

Resolve #100050

During the migration for fleet server we create the .fleet-policies before creating the fleet settings with fleet server hosts. Because of that in cloud this resulted with a .fleet-policies with the fleet.* part.

That PR fix it.

How to test

with a cloud config in kibana.dev.yml

xpack.cloud.enabled: true
xpack.cloud.id: 'staging:dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRjZWM2ZjI2MWE3NGJmMjRjZTMzYmI4ODExYjg0Mjk0ZiRjNmMyY2E2ZDA0MjI0OWFmMGNjN2Q3YTllOTYyNTc0Mw=='
xpack.cloud.deployment_url: '/test/deployment-1'
xpack.cloud.base_url: 'http://test.fr'

• start kibana 7.12 and es 7.12 (you can use that command to persist data for the migration yarn es snapshot --license trial --password changeme -E xpack.security.authc.api_key.enabled=true -E path.data=/tmp/es-data)
• setup agents in kibana 7.12
• Start kibana and ES on that branch
• Visit the fleet plugin
• Check policies contains the fleet.* part. (GET .fleet-policies/_search in the devtools)

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[nchaulet]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: c9c4cb1
• Storybooks Preview

Metrics [docs]

Unknown metric groups

References to deprecated APIs

id	before	after	diff
canvas	29	25	-4
crossClusterReplication	8	6	-2
fleet	22	20	-2
globalSearch	4	2	-2
indexManagement	12	7	-5
infra	261	149	-112
lens	67	45	-22
licensing	18	15	-3
maps	286	208	-78
ml	121	115	-6
monitoring	109	56	-53
stackAlerts	101	95	-6
total			-295

History

• 💚 Build #125822 succeeded e20387f

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

cc @nchaulet

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.13
✅	7.x

The backport PRs will be merged automatically after passing CI.