[Fleet] Add registry config for failing Jest integration tests + unskip

[kpollich]

Summary

Closes #192713

Add kibanaVersionCheckEnabled: false to Jest integration test config + unskip failing 9.0 Jest integration tests.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[nchaulet]

LGTM 🚀

[kpollich]

These are failing because of #186781 it looks like

[kpollich]

I ended up setting access: public for the reset policy routes as we often request these are called from Kibana dev tools. We should probably plan to move these to a public/ prefixed endpoint in the future.

[kpollich]

@elasticmachine merge upstream

[kpollich]

@elasticmachine merge upstream

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 0679d55

Failed CI Steps

• FTR Configs #43
• FTR Configs #46

Test Failures

• [job] [logs] FTR Configs #46 / @ess @serverless SecuritySolution Explore Network Tls Test with Packetbeat Tls Test Ensure data is returned for FlowTarget.Source
• [job] [logs] FTR Configs #43 / @ess @serverless SecuritySolution Timeline @skipInServerless Timeline Details Make sure that we get kpi data

Metrics [docs]

✅ unchanged

History

• 💔 Build #249654 failed 3cabeeb
• 💔 Build #249648 failed c9ee040
• 💔 Build #249631 failed 31f5b16
• 💔 Build #248235 failed 577efa9

cc @kpollich

[juliaElastic]

@kpollich I'm wondering if we should update the API routes too, currently the reset APIs include internal in the path.

kibana/x-pack/plugins/fleet/common/constants/routes.ts

Lines 195 to 198 in aa4f430

	export const PRECONFIGURATION_API_ROUTES = {
	RESET_PATTERN: `${INTERNAL_ROOT}/reset_preconfigured_agent_policies`,
	RESET_ONE_PATTERN: `${INTERNAL_ROOT}/reset_preconfigured_agent_policies/{agentPolicyId}`,
	};

And we should update the KB articles that use the reset APIs to use the correct version when using curl.