Closescoder/internal#1030

the flake stems from the fact that we're showing both a toast with the error, and it's being displayed persistently withErrorAlert. sometimes the assert would happen before the toast rendered, allowing the test to pass.

as recently discussed, showing toasts for errors is not a best practice, especially when showing the error persistently withErrorAlert is a good possibility. we're already doing that, so the toast is redundant.