backup-fetch does not pull the latest backup when using LATEST as argument (data loss)

[benmod]

Current behaviour:

• When restoring from an Azure Blob Storage (WABS) bucket containing 14 basebackups (and associated WALs), dating from 20th of June to 3rd of July (and not touched since, the last modified date for each of them is the date of their day of creation), using the argument LATEST as the backup name (to get the latest backup).
• The restore process takes place and completes, but uses the basebackup from the 27th of June. The database then works perfectly but all the data added between the 27th of June and the 2nd of July is lost.
• When specifying the name of the latest basebackup instead (base_xxxx), it restores perfectly with the latest basebackup and function with all the data.

Expected behaviour:

• When restoring from an Azure Blob Storage (WABS) bucket containing 14 basebackups (and associated WALs), dating from 20th of June to 3rd of July (and not touched since, the last modified date for each of them is the date of their day of creation), using the argument LATEST as the backup name (to get the latest backup).
• The restore process should take place and complete with the latest basebackup (dating from 3rd of July) without having to specify it by name. Or throw and explicit error if for some reason the latest basebackup is not accessible.