Outdated Stripe Library causes issues for Restrict Content Pro

At the moment, GiveWP uses the Stripe PHP library version 6.43.1.
On the flip side, the Restrict Content Pro plugin comes with the same library, but version 7.52.0. Since GiveWP loads before RCP, this leads to the old outdated version loading globally, which throws various PHP errors, notices, and deprecated warnings if the other plugin is trying to do something that’s not supported in the old (GiveWP) version.

This was brought up back in 2019 in this thread on GitHub, with an exploration of GiveWP adding a custom namespace to the Stripe SDK. The thread was subsequently closed with a comment from mikejhale:

Since we are going the route of manually initializing the Stripe SDK within the core gateway, we are no longer using the PHPScoper approach to avoid conflicts, therefore we can close this issue.

But looking through the code, in 2021 the Stripe library is very much still being auto-loaded, and without any custom namespacing. Which is leading to the issues I described above.

How can this be resolved? Can we get the library namespaced with something like GiveStripeLib so that only GiveWP is using that version?

Let me know your suggestions.