test: add more e2e tests for device request prompt

[outofambit]

What kind of change does this PR introduce?

Adds some more basic e2e tests for DeviceRequestPrompt. These tests don't involve actual bluetooth connection scenarios since those would be hard to scaffold, but these will exercise more of the code to validate basic functioning and a couple error states. These e2e tests must be run headed since the bluetooth chooser will not launch on headless chrome instances.

Did you add tests for your changes?

It's all tests :)

If relevant, did you update the documentation?

Summary

Building off of #11072 and #11159, this PR adds a few more e2e tests for DeviceRequestPrompt that can be run headed.

Does this PR introduce a breaking change?

Nope.

Other information
cc @thiagowfx

Bug: #11189

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[thiagowfx]

FYI: I just filed #11189 and back-linked all merged PRs so far to it, including this one.

[Lightning00Blade]

LGTM + Two minor comment before we can merge this.

[Lightning00Blade]

LGTM + The Expectations needed to be update and one JS issue fixes - put suggested fixes.
Other then that once CI passes I will merge.

[Lightning00Blade]

While investigating the timeout issue I found some problems:

1. We also need WebBluetooth to be enabled
2. I don't think we can run this in CI environments due to them not having Bluetooth adapter
   2.1. I ran it on my Cloud env and I get Bluetooth adapter not available. while locally I can see the
   pop up appearing

[OrKoN]

@thiagowfx do you have a plan for this? It looks like the feature is not testable on GitHub actions because there are no Bluetooth devices there.

[Lightning00Blade]

Closing this as it seems it not possible to test with GitHub Actions.