feat: add exit animation to mobile dialog drawer

[iykazrji]

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

Screenshots

Before:
https://www.loom.com/share/df896258fff140468e6b809e343efbb7?sid=7120c059-5567-49aa-a4fc-9ecf4052de68

After:
https://www.loom.com/share/81015edf28384c5aad5edd3137ea271b?sid=58f49f6a-b930-4a55-8f23-ddd97f08a3ae

---

PR-Codex overview

This PR enhances the animation capabilities of the Dialog component in the account-kit/react project by adding new animations and improving the rendering logic for the dialog's portal.

Detailed summary

• Added fade-out and slide-down animations to the Tailwind CSS configuration.
• Introduced useLayoutEffect to manage the rendering of the dialog portal based on its open state.
• Utilized useRef for the dialog card reference.
• Updated the dialog's class names to incorporate new animations and transitions.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aa-sdk-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 11, 2024 7:58pm
aa-sdk-ui-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 11, 2024 7:58pm

[moldy530]

looks good, but can we avoid using the 3rd party library?

using the viewTransition api directly might be overkill. Can we instead either,

1. remove the isOpen ? ... piece, always render the portal, and just selectively add the slide up or down animation based on the isOpen property
2. useEffect triggered by changes on the on isOpen. This will in turn programmatically start the animation (up or down). If the animation is down, then on animation finished, remove the portal if we don't want it always rendered. Probs would need some internal show state as well here to handle this.