git-retry tool or git.retry config (built-in implementation)?

Dear Git Gurus,

In DataLad (https://datalad.org) we are doing lots of automated cloning, fetching etc as part of our CI etc jobs. Once in a while git operations fail [see e.g. 1], and beg us to retry but we need to know when to do so, and not do it upon every failed git invocation since some failures could be legit (repository is gone). While looking how others solve it we found https://stackoverflow.com/questions/35014012/git-retry-if-http-request-failed which pointed to tools like git-retry and later part of https://chromium.googlesource.com/infra/infra/+/HEAD/go/src/infra/tools/git/retry_regexp.go which serve as a collection of regexes to be on lookout for to retry.

Would that be the "best" strategy currently?  

As regex matching might eventually break whenever `git` changes anything in the output messages, I wondered if there could be a more robust internal implementation in git itself? Similarly git-annex has annex.retry config setting which sets the count of retries for "retriable" operations.

Do you think something like that could be implemented in git in some foreseable future?

[1] https://github.com/datalad/datalad/issues/7485

Thank you in advance!