chore: Migrate gsutil usage to gcloud storage (#403)

Automated: Migrate {target_path} from gsutil to gcloud storage

This CL is part of the on going effort to migrate from the legacy
`gsutil` tool to the new and improved `gcloud storage` command-line
interface.
`gcloud storage` is the recommended and modern tool for interacting with
Google Cloud Storage, offering better performance, unified
authentication, and a more consistent command structure with other
`gcloud` components. 🚀

### Automation Details

This change was **generated automatically** by an agent that targets
users of `gsutil`.
The transformations applied are based on the [gsutil to gcloud storage
migration guide](http://go/gsutil-gcloud-storage-migration-guide).

### ⚠️ Action Required: Please Review and Test Carefully

While we have based the automation on the migration guide, every use
case is unique.
**It is crucial that you thoroughly test these changes in environments
appropriate to your use-case before merging.**
Be aware of potential differences between `gsutil` and `gcloud storage`
that could impact your workflows.
For instance, the structure of command output may have changed,
requiring updates to any scripts that parse it. Similarly, command
behavior can differ subtly; the `gcloud storage rsync` command has a
different file deletion logic than `gsutil rsync`, which could lead to
unintended file deletions.

Our migration guides can help guide you through a list of mappings and
some notable differences between the two tools.

Standard presubmit tests are run as part of this CL's workflow. **If you
need to target an additional test workflow or require assistance with
testing, please let us know.**

Please verify that all your Cloud Storage operations continue to work as
expected to avoid any potential disruptions in production.

### Support and Collaboration

The `GCS CLI` team is here to help! If you encounter any issues, have a
complex use case that this automated change doesn't cover, or face any
other blockers, please don't hesitate to reach out.
We are happy to work with you to test and adjust these changes as
needed.

**Contact:** `gcs-cli-hyd@google.com`

We appreciate your partnership in this important migration effort!

#gsutil-migration

---------

Signed-off-by: gurusai-voleti <gvoleti@google.com>

Author: gurusai-voleti

README.md

@@ -27,7 +27,7 @@ support](https://cloud.google.com/support).**
 > **⚠️ WARNING!** The Node.js runtime has [known issues with unicode characters
 > in filepaths on Windows][nodejs-unicode-windows]. There is nothing we can do
 > to fix this issue in our GitHub Action. If you use unicode or special
-> characters in your filenames, please use `gsutil` or `gcloud` to upload
+> characters in your filenames, please use `gcloud`  to upload
 > instead.
 
 ### For uploading a file
@@ -279,7 +279,7 @@ If `parent` is set to `false`, it wil be uploaded to `gs://bucket-name/folder2/f
     Settable fields are: `cache-control`, `content-disposition`,
     `content-encoding`, `content-language`, `content-type`, `custom-time`. See
     [the
-    document](https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata#settable-fields;-field-values)
+    document](https://docs.cloud.google.com/storage/docs/metadata)
     for details. All custom metadata fields must be prefixed with
     `x-goog-meta-`.
 

action.yml

@@ -126,7 +126,7 @@ inputs:
       Settable fields are: `cache-control`, `content-disposition`,
       `content-encoding`, `content-language`, `content-type`, `custom-time`. See
       [the
-      document](https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata#settable-fields;-field-values)
+      document](https://docs.cloud.google.com/storage/docs/metadata)
       for details. All custom metadata fields must be prefixed with
       `x-goog-meta-`.
     required: false