Cloudflare PHP SDK is abandoned, affects v1 and v2

I'll start taking a look on suggestion of the Comment on Github, wherein Cloudflare indicates the usage of API directly.

I've provided a fork removing Cloudflare SDK dependency, for that I've chosen to bring to Cloudflare Drupal module the SDK needed code - in which is the one related to Zone (listing and caching purge).

It was validated using a Drupal vanilla installation, everything worked smoothly after applying #3346396 - admin/config/services/cloudflare Slow to Load 🐛 admin/config/services/cloudflare Slow to Load RTBC solution.

Note
Since SDK code followed an Object-Oriented Programming, I've kept as is. Even though at the end it looked a complex solution to a simple need, it can provide flexibility porting more code from that library on the future.

oof. I'm going to end up being "that guy that just maintains automated builds of OpenAPI libraries because companies can't be bothered to build a CI."

I'll get something built that can be used as a replacement.

I don't think that copying code from the SDK is a good idea - SDK is old, covers a lot of API endpoints and have a lot of complexity for various use case this module should not need to care about.

Before diving into the solution we need to map out what API endpoints we are actually need to interact with and possibly create child issue to split the work where possible.

I'm not sure, but it feels like this type of change should warrant major version number increase.

And in any case, we need to get 📌 Add Drupal Gitlab templates Needs work merged first.

@RoSk0++ to only bringing in what you need from the SDK. And yes new major sounds like a good idea.

Is maybe Cloudflare SDK not death?

During last composer update I saw a new release 1.4.0 of cloudflare/sdk and also its repo on Github has some activity again. Maybe we should double check this with CF or maintainers of this SDK.

https://github.com/cloudflare/cloudflare-php