HIVE-27299: Upgrade guava version to 31.1-jre to fix CVE

[Aggarwal-Raghav]

What changes were proposed in this pull request?

Upgrade guava to fix the CVE's

Why are the changes needed?

The guava version in Hive master branch is 22.0 which has 2 Direct CVE:
CVE-2020-8908
CVE-2018-10237
Component like Tez 0.10.2 (used in hive) has also moved to 31.1-jre of guava version.

Does this PR introduce any user-facing change?

No

How was this patch tested?

By building hive on local machine

[aturoczy]

It is a fair change to fix the CVE's, but I have doubt it will be as easy as the change. The Guava 16 was released in 2014, the 31 is released somewhere in early 2023. After 9 years, I think there will be several breaking change that needs to adjust in the hive side. It should be a huge, but respectful task.

cc: @abstractdog@ayushtkn@deniskuzZ

[ayushtkn]

have played with guava in the past, to chase hadoop upgrade. but hive has too many dependencies with different guava versions, so that didn't work well.
So, ultimately I shaded guava in hadoop for hive and we moved to the hadoop version in which guava was shaded.

@Aggarwal-Raghav no point running the tests again and again those are genuine errors, guava upgrade ain't just a change in the pom

[Aggarwal-Raghav]

Thanks for letting me know @ayushtkn. I was not aware of this.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[aturoczy]

Please close this PR as I think it is won't be resolvable soon.