fix: client-side exception during signup due to nested toast container

[rohan-chaturvedi]

🔍 Overview

There are currently 2 <ToastContainer/>s for react-toastify. One at the root layout, and one within the [team] layout which is theme-aware. This causes a client-side exception when a toast originating in the root layout container is still active, and the route changes to [team]/*. This was most commonly experienced during signup, when redirecting to the org home page.

💡 Proposed Changes

Remove the nested toast container in the team layout.

📝 Release Notes

Fixed a bug during signup that cause a client-side exception.

🎯 Reviewer Focus

Run through the signup process. Observe that the toast drawn on signup remains active once redirected to org home, and no client-side exception occurs

➕ Additional Context

This change makes toasts 'dark' theme regardless of the console theme selection. We will revisit this in the future.

💚 Did You...

• Ensure linting passes (code style checks)?
  - [ ] Update dependencies and lockfiles (if required)
  - [ ] Regenerate graphql schema and types (if required)
• Verify the app builds locally?
• Manually test the changes on different browsers/devices?