[Bug]: nsv will fail to calculate the next semantic version if running against a shallow clone on a monorepo project

[purpleclay]

What happened?

Ensure nsv detects whether the current git repository is a shallow clone. By default, it should automatically pull the entire commit history and all tags. Add a new CLI flag and environment variable that disables auto-fixing of a git clone and instead allows nsv to fail with the appropriate error message.

Steps to reproduce it

1. Run nsv on a CI platform like GitLab that performs a shallow clone by default. Once the history reaches a specific size, the next calculated version will be incorrect (it will effectively reset if tags are missing).

Which version?

v0.10.1

Which operating system(s) are you using?

All

Code of Conduct

• I agree to follow this project's Code of Conduct