[UI Tests] Added a UI test for "Pages" dashboard card navigation.

[pachlava]

Description

Following the maximum similarity to its iOS counterpart, this PR adds a UI test for the "Pages" dashboard card:

What the test does:

@Test
fun e2ePagesCardNavigation() {
    MySitesPage()
        .scrollToPagesCard()
        .assertPagesCard()
        .assertPagesCardHasPage("Blog")
        .assertPagesCardHasPage("Cart")
        .assertPagesCardHasPage("Shop")
        .tapPagesCard()
        .assertPagesScreenLoaded()
        .assertPagesScreenHasPage("Blog")
        .assertPagesScreenHasPage("Cart")
        .assertPagesScreenHasPage("Shop")
}

There is some noise because I moved 3 dashboard-related mock files to a dashboard folder, and also renamed them.

To test

• All tests are green on CI, including the new e2ePagesCardNavigation

Regression Notes

I'm not filling the regression notes since the PR adds a UI test, it does not change the app behaviour in any way.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr18578-691f307
	Commit	691f307
	Direct Download	jetpack-prototype-build-pr18578-691f307.apk

Note: Google Login is not supported on these builds.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr18578-691f307
	Commit	691f307
	Direct Download	wordpress-prototype-build-pr18578-691f307.apk

Note: Google Login is not supported on these builds.

[pachlava]

I added this function with #18345, this I have no idea why this line was here, it makes no sense 😕. This worked only because the Domains card was already on-screen, and did not require scrolling.

[pachlava]

Just moved it a few lines below, so that it belongs to the same card-related functions.

[jostnes]

added one non-blocking question related to , but other than that test works well locally and CI and is similar to the iOS implementation (which is approved) so it's a ✅ for me!

[jostnes]

Suggested change

	ViewMatchers.withId(R.id.my_site_card_toolbar_title),
	ViewMatchers.withId(R.id.my_site_card_toolbar_title)

i noticed that for multiple matches, the last matcher ends with a , which looks odd to me since it's the last one. is this intentional or is it a kotlin thing?

[pachlava]

In this particular case, this is most probably a result of me moving things around. Such a comma in the end, even if it's not followed by another line, is not considered a code style violation. I saw cases when people deliberately kept commas at the end of a line, to avoid extra noise in the future PRs when they add a next line (I left once a nitpick about this here in a PR of yours).