feat(git_utils): Allow configurable shallow clone depth in git_cmd_clone

[lexfrei]

This PR enhances the git_cmd_clone function in git_utils.py by adding a new optional parameter depth (default value: 1). This allows users to customize the depth of the shallow clone, enabling faster cloning and reduced data transfer. The default behavior remains unchanged, ensuring backward compatibility.

Changes:
• Updated the function signature of git_cmd_clone to include depth: int = 1.
• Modified the git clone command to use the provided depth value with the --depth flag.
• Retained the --single-branch option for cloning only the default branch.

Rationale:
Introducing a configurable clone depth provides flexibility for users who may need to fetch more or fewer commits based on their specific requirements. This optimization can lead to significant speed improvements and reduced network load when working with large repositories or in environments with limited bandwidth.

Testing:
• Verified that cloning with the default depth (1) functions correctly.
• Confirmed that specifying different depth values works as expected.

Additional Context:
This change aims to improve performance and user control during repository cloning without disrupting existing workflows.

[dw-0]

Thank you for the PR and for that detailed description. I think this is a good idea and as you can see this is a feature that was requested for a long time. Though, im currently not sure if there will be a significant downside if we make depth 1 the default.
We need to make sure that installs through KIAUH are compatible with Moonrakers own update mechanics, i will get in touch with Moonrakers maintainer and ask if he sees any downside.

One thought i had was, if we should show the user a dialog if he want's to do a shallow clone or not, with a user friendly and not too technical description about what that means and when it would be usefull to do that.

[lexfrei]

A little update for a function. Now you can use it anywhere without any behavior changes and set the depth and branch options where it's already safe. Also, fully documented in code.

P.S. I was so frustrated with the full clone that I didn’t check any issues and just submitted this PR to your repository. I’m glad to see I’m not the only one and that the issue has already been opened.

[dw-0]

Hi, so i had a talk with the Moonraker maintainer. We shouldn't use shallow clones at all.
There is no guarantee that Moonraker, or precisely the update manager of Moonraker, will correctly work 100% of the time. The issue with shallow clones seems to be, that they do not report their version correctly when using git describe (something that Moonraker uses) as there may be no tags available.

The general recommendation was to use a blobless clone instead which would reduce download size and be faster than a regular clone. Also, it was said that there should be no general issue with using the blobless clone by default, so that could become the new default way of cloning. Moonraker itself uses blobless clones with the update managers "hard reset" functionality.

https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone (see "Quick Summary")