Fix/recover from failed branch deletions

[oatymart]

Follow-up to #134

I noticed our release-packages.yml workflow failing in a few places:

1. eslint-config-tao error in run, blocked NPM publish

➡ Clean up the place
Error: Error: To https://github.com/oat-sa/eslint-config-tao
!	:refs/heads/release-4.0.0	[remote rejected] (cannot lock ref 'refs/heads/release-4.0.0': unable to resolve reference 'refs/heads/release-4.0.0')
❎ To https://github.com/oat-sa/eslint-config-tao
Done
Pushing to https://github.com/oat-sa/eslint-config-tao
POST git-receive-pack (1[88](https://github.com/oat-sa/eslint-config-tao/actions/runs/10793376619/job/29935154252#step:4:89) bytes)
error: failed to push some refs to 'https://github.com/oat-sa/eslint-config-tao'
!	:refs/heads/release-4.0.0	[remote rejected] (cannot lock ref 'refs/heads/release-4.0.0': unable to resolve reference 'refs/heads/release-4.0.0')
Done

2. read-aloud-client-fe error in run, blocked NPM publish

➡ Clean up the place
❎ To https://github.com/oat-sa/read-aloud-client-fe
!	:refs/heads/release-0.9.0	[remote rejected] (cannot lock ref 'refs/heads/release-0.9.0': unable to resolve reference 'refs/heads/release-0.9.0')
Error: Error: To https://github.com/oat-sa/read-aloud-client-fe
!	:refs/heads/release-0.9.0	[remote rejected] (cannot lock ref 'refs/heads/release-0.9.0': unable to resolve reference 'refs/heads/release-0.9.0')
Done
Pushing to https://github.com/oat-sa/read-aloud-client-fe
POST git-receive-pack (188 bytes)
error: failed to push some refs to 'https://github.com/oat-sa/read-aloud-client-fe'

Done

3. live-design-system error in run

➡ Clean up the place
⚠ Cannot delete branch release-21.3.0: Error: Pushing to https://github.com/oat-sa/live-design-system
error: unable to delete 'release-21.3.0': remote ref does not exist
error: failed to push some refs to 'https://github.com/oat-sa/live-design-system'
 - Error: Pushing to https://github.com/oat-sa/live-design-system
error: unable to delete 'release-21.3.0': remote ref does not exist
error: failed to push some refs to 'https://github.com/oat-sa/live-design-system'

Based on the error messages, I think it could be the same problem that was addressed in #134 (but we should catch more error messages than we do).

This PR is a bit of a shot in the dark (untested). Looking for a second opinion before propagating to one of the broken workflows.

[github-actions]

Coverage Report

Totals
Statements:	46.65% ( 781 / 1674 )
Methods:	35.06% ( 95 / 271 )
Lines:	45.67% ( 427 / 935 )
Branches:	55.34% ( 259 / 468 )

[oatymart]

There is a second possibility, using if (gitClient.hasBranch) and no error.message check, instead of try/catch.

[gabrielfs7]

Thanks @oatymart

[jsconan]

It is worth a try. However, if a further git action is needed and the refs cannot be resolved it might still break on the next step. Let's see how it goes.