Retrieve and restore actions are available on WebUI before the content is really moved to Glacier

Description

When a user requests to move a document into Glacier, the process behind is asynchronous and it can take hours or days (depending on S3 Glacier lifecycle configuration) before the file is really on S3 Glacier.

Waiting for that, the content remains on S3 and so, the actions specific to Glacier (retrieve, restore) are not available on storage side. But, into WebUI, those actions are available since the user has requested the transfer to Glacier.

So, in some cases, this user or another one could request a retrieve or a restore before the file is on Glacier. Then, it fails and the user is informed that it didn't work (without explanation).

Expectation: the retrieve and restore actions should not be available on WebUI before the file is really on S3 Glacier. 

Steps to reproduce

1. As an AWS admin, configure Glacier lifecycle to 0 days
2. With a granted user, go to the Nuxeo instance with the glacier addon
3. Create a document with a binary file
4. Click on the Move to Glacier action
5. Wait for 24 hours
6. Go back to the document

Observed result

3. there is a header on the document to inform the user that the document has been moved to Glacier

3. the retrieve action is available on the WebUI

3. the restore action is available on the WebUI

6. the retrieve action is available on the WebUI

6. the restore action is available on the WebUI

Expected result

3. there is a header on the document to inform the user that the document has been moved to Glacier

3. the retrieve action is NOT available on the WebUI

3. the restore action is NOT available on the WebUI

6. the retrieve action is available on the WebUI

6. the restore action is available on the WebUI