Add safe.directory in failure handler

[BDevParity]

Summary

• Fix resume validation in publish crates workflow by using local ref check (git branch -r) instead of git ls-remote, which fails because
  persist-credentials: false prevents remote access

Context

• Failed run: https://github.com/paritytech-release/polkadot-sdk/actions/runs/236
  20337279/job/68797902086#step:25:20

[github-actions]

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

• Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
• Should be a legit fix for some bug, not adding tons of new features.
• Must either be already audited or not need an audit.

Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.