[Fleet] Backport lock manager service usage

[nchaulet]

Summary

Backport #219113

We are hitting some retries issue during setup, and relying on the lock manager service as we do in 9+ version seems to be more reliable

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[Supplementing]

Looking at the original PR, this one is missing the changes to tsconfig.json. Are they needed here? https://github.com/elastic/kibana/pull/219113/files

[Supplementing]

Also, do we need to bring in the changes from #219220 that expose lockManager as a package? I see it was a dependency for the original PR, so not sure if that will have any effect on these changes.

[Supplementing]

See my comments, but otherwise, LGTM 🚀

[nchaulet]

Also, do we need to bring in the changes from #219220 that expose lockManager as a package? I see it was a dependency for the original PR, so not sure if that will have any effect on these changes.

Luckily this one was already backported to 8.19,

Looking at the original PR, this one is missing the changes to tsconfig.json. Are they needed here? https://github.com/elastic/kibana/pull/219113/files

Yes they are, I just updated

[Supplementing]

Luckily this one was already backported to 8.19,

I saw the backport had failed but missed where it succeeded, thanks for clarifying!

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 27aa54b

Failed CI Steps

• Jest Tests #4

Test Failures

• [job] [logs] Jest Tests #4 / Connector renders correctly

Metrics [docs]

✅ unchanged

cc @nchaulet

[jlind23]

@kpollich @Supplementing @nchaulet can we please get his backport merge as soon as we can?