feat(manager): add sveltos manager

[oliverbaehler]

Changes

This adds the manager for sveltos for GitOps managed Cluster Fleets. Essentially we have the same functionality as argoCD, so we were able to take the argocd manager and adjust the schema etc. I hope that's okay.

Context

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

Not sure if there's more?

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[secustor]

Package manager details can be found here: #30090 (comment)

[secustor]

Is this ready for another review?
Please use the re-review button so we maintainers know that you are ready for a new review.

BTW It isn't necessary to merge main if there are no conflicts.

[oliverbaehler]

@secustor Yes this is ready for review, Sorry!

[secustor]

Needs code coverage ( see the failing CI ) and docs changes requested by @HonkingGoose

[secustor]

You are missing coverage.

[oliverbaehler]

Hi I am sorry I am unable to get the coverage up :( . Can I somehow create the coverage locally? What i currently do is run Jest:

pnpm jest lib/modules/manager/sveltos
...
Statements   : 2.39% ( 1023/42686 )
Branches     : 0.36% ( 49/13404 )
Functions    : 0.51% ( 27/5294 )
Lines        : 2.42% ( 1020/42083 )

But i don't know how to interpret these results..

[rarkins]

renovate/docs/development/local-development.md

Lines 157 to 166 in 9b64288

	### Coverage
	The Renovate project maintains 100% test coverage, so any Pull Request will fail if it does not have full coverage for code.
	Using `// istanbul ignore` is not ideal, but can be a pragmatic solution if adding more tests wouldn't really prove anything.
	To view the current test coverage locally, open up `coverage/index.html` in your browser.
	Do not let coverage put you off submitting a PR!
	Maybe we can help, or at least guide.
	Also, it can be good to submit your PR as a work in progress (WIP) without tests first so that you can get a thumbs up from others about the changes, and write tests after.