Plugin Browse: Update e2e test to check URL with selected site

[WBerredo]

Fixes #66637
Related to #66636

Proposed Changes

Add URL check at the end of the Category selection e2e test.
This guarantees the site URL will always be present on this action.

Testing Instructions

Check if all checks are passing. Including e2e tests.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-74945

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-74945&env=jetpack

[matticbot]

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

[worldomonation]

Approved, but with a non-blocking nit/question.

[worldomonation]

nit:non-blocking - a small question, is the intention to make sure the site slug comes at the end?

In any case, the 'g' flag doesn't seem necessary from my experience. Have you run into faulty results without it?

[WBerredo]

is the intention to make sure the site slug comes at the end?

The intention was to make a more specific regex as the bug it was trying to solve was that it being redirected to /plugins/browse/seo. So in the past, if we had used /plugins/browse/seo as regex the test would still be passing because we didn't specify the URL must end with it.

In this case, as we are specifying siteURL, we don't have any case currently where it might fail, so let me know if you prefer to remove it.

the 'g' flag doesn't seem necessary from my experience

That's right, I removed it 9266509