Improve release.sh script

### Is your feature request related to a problem?

When we release for a first time, we create a tar.gz archive that we place in the release folder, and when we run the upgrade, erlang untar this archive and run the upgrade.

But if the upgrade fail, and we fix the issue in the same version, when we create the new release and try to upgrade, erlang say that the release is already unpacked and so the new fix isn't applied.

### Describe the solution you'd like

To fix this in the release script, when we put the archive in the release folder, if the release seems already unpacked, then we can direclty untar the archive, so the next upgrade will take the same version with the hotfix

### Additional context

_No response_

### Epic

_No response_

Start by inspecting release.sh and the release archive and upgrade flow described in the issue. Reproduce the case where a failed upgrade leaves the release unpacked, then verify that creating a replacement archive for the same version allows the next upgrade to apply the hotfix.

Written by the indexing model from the issue text.