Replace container-runtime with client-go

[stlaz]

What type of PR is this?

/kind feature

What this PR does / why we need it:
This PR removes controller-runtime as a dependency for the repository. The controller is rewritten using client-go in a pattern that most kube maintainers are familiar with.

This way we remove a lot of indirection in the controller logic that would make it hard to investigate failures in the future.
Logic primitives common for core kube controllers, like informers and listers, are being used instead of mystical "Getters" that shadow whether a given resource was retrieved from local cache or via a live API request.
Use of typed clients is introduced, and typed clients are generated for the SecretSync resource, making it easier for external use.

Which issue(s) this PR fixes:
Fixes #13, though the main purpose is to simplify future maintenance of the controller

Special notes for your reviewer:
Built on top of the refactorings from #173

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stlaz
Once this PR has been reviewed and has the lgtm label, please assign enj for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

This issue is currently awaiting triage.

If secrets-store-sync-controller contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 26.31579% with 560 lines in your changes missing coverage. Please review.
✅ Project coverage is 28.29%. Comparing base (9f4597d) to head (09e9227).
⚠️ Report is 78 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/controller/secretsync_controller.go	51.79%	103 Missing and 18 partials ⚠️
cmd/main.go	0.00%	103 Missing ⚠️
client/informers/externalversions/factory.go	0.00%	80 Missing ⚠️
client/clientset/versioned/clientset.go	0.00%	39 Missing ⚠️
pkg/leaderelection/leaderelect.go	0.00%	35 Missing ⚠️
...ned/typed/secretsync/v1alpha1/secretsync_client.go	0.00%	34 Missing ⚠️
...externalversions/secretsync/v1alpha1/secretsync.go	0.00%	27 Missing ⚠️
...nt/clientset/versioned/fake/clientset_generated.go	0.00%	25 Missing ⚠️
.../typed/secretsync/v1alpha1/fake/fake_secretsync.go	0.00%	14 Missing ⚠️
pkg/util/secretutil/secret.go	63.15%	10 Missing and 4 partials ⚠️
... and 12 more

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #186       +/-   ##
===========================================
- Coverage   56.32%   28.29%   -28.04%     
===========================================
  Files          12       24       +12     
  Lines        1051     1145       +94     
===========================================
- Hits          592      324      -268     
- Misses        415      787      +372     
+ Partials       44       34       -10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[k8s-ci-robot]

@stlaz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-secrets-store-sync-controller-image-scan	09e9227	link	false	/test pull-secrets-store-sync-controller-image-scan

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.