Fix compute domain release after function and site deletion - #13691

Deleting a function or site currently leaves its proxy rules until the deletion worker runs. That delays domain reassignment and can make old domains appear on a resource created with the same public ID.

Remove owned rules before returning from resource deletion, matching the project, resource type, and internal resource identity. Keep the resource cleanup job queued before immediate rule removal, and defer provider/certificate cleanup using the removed rule snapshot. Routing also rejects stale or missing deployment resource identity with the existing resource-not-found response.

Fixes #8068.

This draft depends on safe deferred cleanup that preserves routing and provider configuration for a reassigned domain, and preserves any certificate still referenced by a live rule. It should be retargeted to main once that behavior is available there.

Validation:

• Deployment, certificate, and worker-job library tests: 39 passed, 48 assertions, including 16 new deployment ownership cases.
• Pint and Rector passed for changed files. PHPStan passed for the eight changed library/action/test files; the router file has the same pre-existing constant-false execution-retention warning at line 794 as the exact base.
• Added API regressions for immediate release, ID reuse, reassignment, unrelated resources, redirects, and branch/generated domains, plus delayed-worker regressions for reused rule IDs and cross-project reassignment.
• At head 83c958a019, CI Checks passed; Unit passed (1,195 tests, 6,002 assertions); General passed (42 tests, 240 assertions, 10 unrelated skips), including all four new delayed cleanup cases; Proxy passed (62 tests, 1,222 assertions, plus 12 internal tests with 105 assertions). Functions, Sites, schedules, and the other affected API suites also passed.
• Three unrelated CI failures remain: GraphQL AvatarsTest::testGetImageFromURL receives JSON instead of an image from its external-image request; Avatars testGetImage fails in all three scopes with HTTP 404 instead of 200 for https://appwrite.io/images/open-graph/website.avif; S3 setup fails before tests because the runner cannot pull minio/minio. The draft status is retained.
• Local Docker remains unavailable; the full API and registered deletion-worker validation above ran in CI. The local unit run passed; full platform initialization locally requires native Swoole\Http\Response.