feat: shallow clone in argo repo server

[Ani1357]

📌 Summary

🔍 Reviewer Notes

🧹 Checklist

• Code is readable, maintainable, and robust.
• Unit tests added/updated

[svcAPLBot]

Comparison of Helm chart templating output:

@@ metadata.labels.argocd.argoproj.io/secret-type @@
# v1/Secret/argocd/argocd-repo-creds-gitea
! ± value change
- repo-creds
+ repository

@@ metadata.labels.argocd.argoproj.io/secret-type @@
# v1/Secret/argocd/argocd-repo-creds-gitea-internal
! ± value change
- repo-creds
+ repository

@@ (root level) @@
# v1/Secret/argocd/argocd-repo-apl-core
! + one document added:
+ ---
+ # Source: raw/templates/resources.yaml
+ apiVersion: v1
+ data:
+   name: YXBsLWNvcmU=
+   url: aHR0cHM6Ly9naXRodWIuY29tL2xpbm9kZS9hcGwtY29yZS5naXQ=
+   depth: MQ==
+   project: ZGVmYXVsdA==
+   type: Z2l0
+ kind: Secret
+ metadata:
+   name: argocd-repo-apl-core
+   namespace: argocd
+   labels:
+     app: raw
+     app.kubernetes.io/instance: argocd-artifacts
+     app.kubernetes.io/managed-by: Helm
+     app.kubernetes.io/name: raw
+     app.kubernetes.io/part-of: otomi
+     app.kubernetes.io/version: 0.2.3
+     argocd.argoproj.io/secret-type: repository
+     helm.sh/chart: raw-0.2.3

[j-zimnowoda]

There is memory usage improvement by around 60MB

Also cross-checked the labels with the documentation: https://github.com/bitnami-labs/sealed-secrets#sealedsecrets-as-templates-for-secrets

All good.

[j-zimnowoda]

Noticed that argocd is reporting issues while connecting via public gitea url. The main branch does not carry this problem.

[CasLubbers]

The result of the failing repositories is that my applications stay in unknown with the following error:
ComparisonError
Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = failed to list refs: authentication required: Unauthorized

[CasLubbers]

See my comment