[FR] Assess whether we should use Cloud Run's built in GCS volume mount feature in place of GCSFuse directly

Should we use Cloud Run's built in [GCS volume mount feature](https://cloud.google.com/run/docs/configuring/services/cloud-storage-volume-mounts) on the pcap sidecar container instead of GCSFuse directly?

The advantage it provides is when developers look at the sidecar container in the console they'll see the Volume mount configured and it will just make the sidecar make a bit more sense for folks that don't read the README carefully. I also suspect it will check GCS IAM permissions for us and have better error messages in that regard.

For non Cloud Run environments we'll still have to use GCSFuse directly and built out a function to detect the execution env. Alternatively, guard this option with yet another flag.

Review the README and the current pcap sidecar setup that uses GCSFuse directly. Compare Cloud Run's built-in GCS volume mount behavior with the non-Cloud Run path and determine whether environment detection or an additional flag is needed; done means documenting a clear recommendation and implementation scope.

Written by the indexing model from the issue text.