fix(ui): add missing deps

[aklkv]

Description

resolve: #26801

While migrating to pnpm which has much stricter dependancies resolution rules we missed a couple of deps that needs to be explicitly installed such as one that broke flyout component @ember/test-helpers

Testing & Reproduction steps

Links

NMD-1004

Contributor Checklist

• Changelog Entry If this PR changes user-facing behavior, please generate and add a
  changelog entry using the make cl command.
• Testing Please add tests to cover any new functionality or to demonstrate bug fixes and
  ensure regressions will be caught.
• Documentation If the change impacts user-facing functionality such as the CLI, API, UI,
  and job configuration, please update the Nomad website documentation to reflect this. Refer to
  the website README for docs guidelines. Please also consider whether the
  change requires notes within the upgrade guide.

Reviewer Checklist

• Backport Labels Please add the correct backport labels as described by the internal
  backporting document.
• Commit Type Ensure the correct merge method is selected which should be "squash and merge"
  in the majority of situations. The main exceptions are long-lived feature branches or merges where
  history should be preserved.
• Enterprise PRs If this is an enterprise only PR, please add any required changelog entry
  within the public repository.

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

[jrasell]

Hi @aklkv and thanks for raising this. Are you able to take a look into the failing tests please?

[aklkv]

@jrasell I have, and consulted with @philrenaud and it seems to be known flaky test

[philrenaud]

Confirming that it's flakey but eventually passes on rerun, yes?

[aklkv]

for the life of me I can't reproduce it locally to try to fix it as it's just passes locally 😔

[philrenaud]

It's a timed test by its very nature ("make sure a user gets a notification that their token is soon to time-out!") which makes it implicitly a little flakey, but I've been shocked at how flakey it's become over time. It has gone from a 99% pass rate to something like 10% over the past year or so.

It would not be unreasonable to rewrite the test to be more isolated, or even to abstract away the timer and pass in a boolean to the test component indicating it should show a warning or something.

[jrasell]

I've skipped the test on main and raised a followup backlog ticket for it. @aklkv do you mind merging main into this branch which should clear up the test failure and add a changelog entry, as this fixes a user facing bug. We have the make cl command available for this.

[jrasell]

LGTM, thanks @aklkv!

I've tested this out locally too and can see it fixed the linked issue.