fix(ui): resolve Zod schema parsing issue on domain transfer

[unrenamed]

What does this PR do?

Fixes #1674.

Root Cause

Domain Zod schema is parsing a Prisma update response that don't have a required field: registeredDomain (it can be null, but not undefined). And it does that after updating the DB and adding a record to QStash, thus returning an error but proceeding to complete the transfer (eventually sending a success email).

This issue seems to be common for both verified and unverified domains.

Fix

For consistency with other domain operations like delete, I kept the Prisma response parsing and included registeredDomain entity into the response using Prisma's include option.

Also, this PR fixes a typo in the domain transfer error message. Looks like it was copied from the domain delete API route.

How to test?

1. Log into the application and create a new workspace if you only have one.
2. Navigate to your main workspace domain management: Settings > Domains
3. If you don't have a domain, add a new one.
4. Transfer an unverified domain to a different workspace.
5. You should see a toast with a success message.

[vercel]

@unrenamed is attempting to deploy a commit to the Dub Team on Vercel.

A member of the Team first needs to authorize it.

[unrenamed]

@steven-tey This one is ready for peer review

[unrenamed]

@steven-tey @TWilson023 just in case this slipped through, I'd highly appreciate it if you review and merge (if all is good) this and #1687 before the end of the event.