Testing: Update mocks for screenshot test

[rachelmcr]

As noted in #11666 the screenshot test currently fails due to errors with the mocks. This PR updates the mocks to resolve those errors so the test passes.

Only one review is needed and anyone can review.

To test:

• Run ./gradlew :WordPress:connectedVanillaDebugAndroidTest and confirm all tests pass.
• You can also run WPScreenshotTest (under WordPress/src/androidTest/java/org/wordpress/android/ui/screenshots/) individually to confirm it passes.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[peril-wordpress-mobile]

	Warnings
⚠️	PR is not assigned to a milestone.

Messages

📖

This PR contains changes in the subtree libs/mocks/. It is your responsibility to ensure these changes are merged back into wordpress-mobile/WordPressMocks. Follow these handy steps! WARNING: Make sure your git version is 2.19.x or lower - there is currently a bug in later versions that will corrupt the subtree history! cd WordPress-Android git checkout fix/wpscreenshot-test-mocks git subtree push --prefix=libs/mocks/ https://github.com/wordpress-mobile/WordPressMocks.git merge/WordPress-Android/11669 Browse to https://github.com/wordpress-mobile/WordPressMocks/pull/new/merge/WordPress-Android/11669 and open a new PR.

Generated by 🚫 dangerJS

[peril-wordpress-mobile]

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

[peril-wordpress-mobile]

You can test the changes on this Pull Request by downloading the APK here.

[rachelmcr]

Note: I'm currently ignoring this Peril message:

This PR contains changes in the subtree libs/mocks/. It is your responsibility to ensure these changes are merged back into wordpress-mobile/WordPressMocks. Follow these handy steps!

We have discussed splitting the Android and iOS mocks, because the API calls aren't always identical and keeping them synced can be a challenge. Although we haven't started formally splitting them (e.g. removing iOS-specific mocks from Android, and vice versa) I think it's ok to start letting the Android mocks diverge from the wordpress-mobile/WordPressMocks repo. WDYT? (Internal ref: paaHJt-PH-p2)

[oguzkocer]

WPScreenshotTest passed without any issues.

I think it's ok to start letting the Android mocks diverge from the wordpress-mobile/WordPressMocks repo.

That sounds OK to me.