While I do agree with your thesis that global options increase likelihood of unexpected interactions, I would strongly emphasize this is not one of them.
In nearly all builds, aside from those running Git history commands like `git rev-parse`, no builds would be affected by this change. For those who are using such a complicated command, the error output would be straightforward enough that they could disable shallow cloning for their pipeline.
The impact of this global action is also pretty obvious for a system administrator who could alleviate burden from maintainers on this project. It can also be disabled by default so that users have to opt-in.
I'll also add that you already have global options for things like `Add git tag action to jobs`. Surely, this is less cryptic and less error-prone than this existing global configuration.
I don't intend to add global configuration options like this.