Apply automatic linter fixes

[andreaskienle]

After #3 this PR applies all automatically fixable rules.

It’s the result after eslint ./src --report-unused-disable-directives --max-warnings 0 --fix

[enrico-kaack-comp]

may you also add a gh action workflow that checks for violations and fails on warnings/errors? we can than include this in the PR test to enforce this rules

[andreaskienle]

may you also add a gh action workflow that checks for violations and fails on warnings/errors? we can than include this in the PR test to enforce this rules

Eventually, we can do this, I think it’s a good idea, but at the moment, we have too many errors. The pull request only fixes those for which there is an automatic solution. What's left are still 33 files with errors, especially about ⁠any in TypeScript, as well as other issues that we should investigate a bit.

My hope is that we can resolve these issues when we modify the files, for example, during the migration to the new backend.

Perhaps we could set a reminder to revisit this topic in a few weeks or months. Additionally, we could run the linter in a GitHub action in warning mode only.

[andreaskienle]

Here’s the follow-up task we talked about: https://github.tools.sap/kubernetes/k8s-lifecycle-management/issues/2142. I hope it's okay that I linked it here.