Asset stuck in quarantined state if HA exception occurs during download when firewall enabled

While doing additional testing for NEXUS-16852 I found that if an exception happened during download (for example due to HA retry conflicts when multiple nodes attempt to cache the same proxied asset) then that asset would remain in a quarantined state of PENDING.

The only workaround I found was temporarily disabling and re-enabling the quarantine capability.

While the HA conflicts during caching should ideally not happen (NEXUS-17497, NEXUS-17496, and NEXUS-13462 are looking at ways to avoid that) it should not be necessary to have to toggle the capability to unstick pending asset requests.

Expected: if an exception causes an asset to be left as quarantined (PENDING) then the firewall request should at least be rescheduled/retried when the asset is next requested.

If automatically retrying the pending asset is not possible based on incoming requests then we should consider adding a UI button to retry all pending requests, so admins can unstick them.

This might also be related to NEXUS-17494

Workaround to un-stick Assets Stuck in Quarantined state of PENDING

Temporarily disabling and re-enabling the quarantine capability.