fix: flaky e2e alert test

[royendo]

• await queryClient.invalidateQueries(...) was blocking the form close and notification toast until the list resources query refetched
• In CI, this total wait (mutation + refetch) could exceed Playwright's 5s assertion timeout, causing the "Should create alert with schedule" e2e test to flake
• Changed to void (fire-and-forget) so the notification appears immediately after the mutation succeeds; the cache still invalidates in the background

Flaky test: https://github.com/rilldata/rill/actions/runs/23904454966/job/69720769909

Checklist:

• Covered by tests
• Ran it and it works as intended
• Reviewed the diff before requesting a review
• Checked for unhandled edge cases
• Linked the issues it closes
• Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
• Intend to cherry-pick into the release branch
• I'm proud of this work!

---

Developed in collaboration with Claude Code

[royendo]

oh the irony of getting flaky e2e tests when trying to fix a flaky e2e test

[AdityaHegde]

Looks like a rerun failed the tests.

I am seeing console errors about submit (we do use use:enhance),

use:enhance must be added to the form to use submit, or pass a HTMLElement inside the form (or the form itself) as an argument

I think the solution would be to make the form creation not be reactive. We would need to re-mount the component every time it is opened. Needs some testing to make sure we update the fields if explore changes.