fix: Google Cloud Storage CheckpointSyncer checker implementation

[maximegris]

Description

The current CLI command hyperlane avs check only checks when storage location starts with s3://

This PR allow to retrieve and check the validator state on Google Cloud Storage - when storage location starts with gs://

Drive-by changes

• Use the latest location set during Validator registration & retrieve it from ValidatorAnnounce.getAnnouncedStorageLocations

Related issues

• None

Backward compatibility

• Yes

Testing

• Manual using locally compiled yarn hyperlane avs check command

Before

Operator name: Born to be wild
Operator address: 0xd38d980188604c7051dbce2980a0c6e38423fda4
Validator address: 0x58a607f46a481c9e5209ab27f45189411fA83D41
Validator is not validating on any chain

After

Operator name: Born to be wild
Operator address: 0xd38d980188604c7051dbce2980a0c6e38423fda4
Validator address: 0x58a607f46a481c9e5209ab27f45189411fA83D41
  Validating on...
  optimism
  Storage location: https://storage.googleapis.com/hyperlane_2okiqlhes2ki6lfsgsa0qlzaclx/gcsLatestIndexKey
  Latest merkle tree checkpoint index: 632213
  Latest validator checkpoint index: 632213

[changeset-bot]

⚠️ No Changeset found

Latest commit: e00bc1d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR