Add Edge Scripting API

[ToshY]

Fixes #144

---

TODO:

• Implement "Edge Scripting API"
• Update docs
• Resolve PR comments
• Manual testing

[ToshY]

Initially thought I had to create this from scratch, but it seems that what was previously known (or available in the API docs) as "Compute scripts" which has now been transformed to "Edge scripts", which can be seen from the endpoints being the same: /compute/script.

Example:

• https://docs.bunny.net/reference/computeedgescriptpublic_index
• https://docs.bunny.net/reference/listedgescriptsendpoint_listedgescriptsbyaccount

So the majority of the existing "Compute" models and endpoints should be moved and renamed to "Edge script" standards. This most likely would be classified as a breaking change, as all existing "Compute" would be moved to the "Edge Scripting" namespace, and would require an instance of the EdgeScriptingAPI class instead of the BaseAPI class.

(As "compute scripts" can not be found searching through the API docs, I'm not sure if it is actually used by anyone. Still a breaking change if it's refactored though; 5.0.0).

[ToshY]

lgtm.

Left todo is testing, and likely fix some issues along the way.

Edit

Tested and already looked good at 7b7d80c

Surprisingly, didn't have to do many code changes. Manual testing seems OK.

[ToshY]

Think merge it tomorrow 💭

Don't forget to update the UPGRADE.md regarding breaking change from compute to edge scripting and introduction of integration endpoint in base.