feat: add tip to separate invite from recovery

[zepatrik]

No description provided.

[CLAassistant]

All committers have signed the CLA.

[Copilot]

Pull request overview

This PR updates the Kratos “Invite users” documentation to suggest using a return_to parameter as a way to differentiate first-time invitations from regular password recovery, by carrying context into the recovery/settings flows.

Changes:

• Adds a new :::tip explaining return_to, including an example request and guidance on using it for invitation branding.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[simi]

Adds a tip to the Invite users guide showing how to pass return_to on POST /admin/recovery/link, so admins can control where an invited user lands after setting credentials — and brand a first-time invitation differently from a normal password reset (e.g. ?return_to=…?source=invitation).

return_to on this endpoint is supported but undocumented on the page where people implementing invitations actually look. It was added to the API spec in ory/kratos#3711 and requested in ory/kratos#3084, yet the invite-users guide never mentioned it. This closes that doc gap and notes the allowed_return_urls allow-list requirement.