feat: implement browsingContext.activate

[OrKoN]

WPT: web-platform-tests/wpt#40964
Spec: w3c/webdriver-bidi#453

[thiagowfx]

TODO for you (either in this PR or in the next one, but keep it in mind): Update

chromium-bidi/src/bidiMapper/domains/context/browsingContextImpl.ts

Line 719 in cfa01d1

await this.#cdpTarget.cdpClient.sendCommand('Page.bringToFront');

...to use the bidi API instead of calling the CDP command directly.

We may end up removing this line altogether at some point, but for now it would be better to use the BiDi API, IMHO.

[thiagowfx]

LGTM (adding one test would be nice).

[jrandolf-2]

+1 to adding a test

[OrKoN]

Added a basic test (more extensive test coverage will be done by WPT)

[thiagowfx]

I would have suggested to add this to the browsing context test file.

The top-level directory for tests/* becomes increasingly messy if we put everything there.

Alternatively, we could mirror WPT and create a top-level browsing_context dir, and move this therein.

(Feel free to re-request review before submitting, I tend to review fast and would have suggested this in advance.)

[OrKoN]

That sounds like a separate issue. Putting everything into the single browsing context test file is messy too.

[thiagowfx]

Do you think it's worth to create many subdirectories, like WPT? We could start to slowly migrate our codebase to a similar pattern.

[OrKoN]

I think subdirectories is the way to go where the directory name is the module name. I think we should not create a directory per command yet (a file per command/event should be okay)