Fix toast component in e2e tests

[ryaplots]

Summary

Fix toasts testing in e2e tests.

Changes

• Add a data-test-id per toast type
• Test per toast type

Testing

Steps

Run e2e tests with a license warning toast always showing.

Results

Regressions

Tests should pass anyway

Notes for Reviewers

In one of the previous CI runs, all the e2e tests were failing due to a warning toast being rendered. This toast was showing because the ci license key was about to expire, which is the correct behavior. However, the e2e tests should not fail in this case, they should be resilient to the UI having more than one toast.

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Testing: The steps/process to test this feature are clearly explained including testing for regressions.
• Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.