refactor: use utopia-php/client 0.5's names

[ChiragAgg5k]

utopia-php/client 0.5 moved Utopia\Client to Utopia\Client\Client and keeps the old name only as an alias until its next major. This PR requires ^0.5 and imports the new name in Deployments, Jobs, Sandboxes and the README, so client can drop the alias.

• The only code changes are those imports, plus Pint's import re-sorting. Behaviour is identical, because the old name is an alias of the same class in 0.5.
• The lock moves utopia-php/client from 0.4.3 to 0.5.1 and nothing else.
• Locally, composer format:check, composer analyze and composer refactor:check pass, and composer test passes 43 tests.

Part of removing client's alias shim (appwrite/appwrite#13828). Appwrite needs an sdk-for-php release with this change before client's next major.

[greptile-apps]

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking gap in observable test coverage for the upgraded HTTP client.

Findings

1.  Real client remains untested ▶

Fix with agent prompt

### Issue 1
composer.json:10
The upgrade changes the HTTP client used when a resource client is constructed without an argument, but the tests inject a PSR-18 test double instead. They therefore cannot catch a problem with constructing or configuring the upgraded client. Please add a test that makes an observable request with the configured client, rather than asserting version pins or source text.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR upgrades utopia-php/client to 0.5.1 and updates the three resource clients and README to import its new client name.

• The changed real-client integration lacks an observable-behavior test; existing resource tests use a PSR-18 double.

_{Reviews (1) · Last reviewed commit: "refactor: use utopia-php/client 0.5's na..."}