🐛 Bug Report: Domains Not Unassigned on Function Delete

[ItzNotABug]

👟 Reproduction steps

Encountered an issue somewhat similar to the one reported in Issue #7999, where domains added to a function persist even after the function is deleted. This occurs under the same conditions as the previously linked issue; however, you can confirm it by checking the domains tab.

---

Steps to Manually Reproduce:
You can manually reproduce the issue by disabling the appwrite-worker-deletes service and following these steps:

1. Initialize a new Function
2. Attach a custom domain to it
3. Delete the function
4. Recreate the function using the same ID.
   The original domain still exists alongside any newly added domain.

---

Additional Issue:
Another related problem is that until the deletion worker processes removals, the domain document exists in the database which prevents the domain from being reassigned to another function instantly.

👍 Expected behavior

Instantly remove the domain or allow its assignment, maybe by checking if the assigned function exists or not by making queried request using $function->getInternalId()?

👎 Actual Behavior

1. Domain re-appears after re-creating a function
2. Unable to assign a domain to any other function until the worker runs

🎲 Appwrite version

Appwrite Cloud

💻 Operating system

MacOS

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct