Fix part of #3245 [A11y] Enabling AccessibilityChecks for PinPasswordActivityTest

[Rohit1173]

Explanation

Fix part of #3245 : Enable Accessibility Checks
Removed the @DisableAccessibilityChecks Annotation from the PinPasswordActivityTest

There were 27 tests with @DisableAccessibilityChecks Annotation in PinPasswordActivityTest
So running these tests after removing it caused an Accessibility error and it said to remove ContentDescription of TextInputeditText inpin_password_activity.xml

I have checked this using Accessibility scanner app too and it also showed the same result

There were 2 tests fun testPinPassword_pinView_hasContentDescription() and
fun testPinPassword_configChange_pinView_hasContentDescription() which check the ContentDescription of the TextinputEditText . So I have to remove these tests
Screenshots after running the tests

Device: Pixel 3a API 28

Device: Pixel C API 28

The only test which was failing was
fun testPinPassword_withUser_forgot_inputAdminPinAndNullPin_imeAction_errorIsDisplayed() and it was failing even before removing ContentDescription and @DisableAccessibilityChecks Annotation and not because of the changes made and the same test passes sometimes while running separately

UI CHANGES

BEFORE	AFTER

Essential Checklist

• The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• Any changes to scripts/assets files have their rationale included in the PR explanation.
• The PR follows the style guide.
• The PR does not contain any unnecessary code changes from Android Studio (reference).
• The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
• The PR is assigned to the appropriate reviewers (reference).

For UI-specific PRs only

If your PR includes UI-related changes, then:

• Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes
• For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see RTL guide)
• Add a video showing the full UX flow with a screen reader enabled (see accessibility guide)
• Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing

[yash10019coder]

@Rohit1173 it seems like a flaky test so I have restarted the ci.

[Rohit1173]

@Rohit1173 it seems like a flaky test so I have restarted the ci.

Thanks, @yash10019coder

[Rohit1173]

@rt4914 @anandwana001 PTAL

[ayush0402]

I had also filed an issue about that failing test at #3771. If it is something that needs to addressed we can re-open that issue.

[rt4914]

LGTM, Thanks @Rohit1173