Problem with gsutil and crcmod on google-cloud-sdk-365.0.0-1.x86_64

[cr...@rootwork.it]

Be warned that google-cloud-sdk-365.0.0-1.x86_64 may cause issues with gsutil on CentOS/RHEL 7. I upgraded from google-cloud-sdk-361.0.0-1.x86_64 and gsutil immediately lost the ability to use compiled crcmod headers. This can be a major issue if you have high-volume workloads that depend on "gsutil rsync" or "gsutil cp." I followed the instructions to reinstall and recompile crcmod  (https://cloud.google.com/storage/docs/gsutil/addlhelp/CRC32CandInstallingcrcmod) but it didn't work. 

I noticed that the latest version of google-cloud-sdk bumps the version of gsutil from 5.4 to 5.5, and ups Python from 3.6 to 3.8. However, the latest version of Python3 on CentOS/RHEL 7 is 3.6.

```

# gsutil version -l

gsutil version: 5.5

checksum: 54a50a74649e27e7568328e5852187f0 (OK)

boto version: 2.49.0

python version: 3.8.11 (default, Sep 29 2021, 17:21:43) [Clang 12.0.1 ]

OS: Linux 3.10.0-1160.45.1.el7.x86_64

multiprocessing available: True

using cloud sdk: True

pass cloud sdk credentials to gsutil: True

config path(s): /etc/boto.cfg,REDACTED

gsutil path: /usr/lib64/google-cloud-sdk/bin/gsutil

compiled crcmod: False

installed via package manager: False

editable install: False

```

I opened a support ticket but thought I'd throw a warning out to people on this list who may get bitten by this unexpected change in a routine package upgrade.

   Craig