Fixes #4539: Replace CaseSensitiveEquals by Equals in dev assets

[masclot]

Explanation

Fixes #4539: Replace the rule type CaseSensitiveEquals by Equals in dev assets. This only affects the topics used in dev environment. The rule type CaseSensitiveEquals is no longer supported.

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

Videos

current	new
fix_for_CaseSensitiveEquals_current.webm	fix_for_CaseSensitiveEquals_new.webm

Screenshots

current	new

[masclot]

I tested this by running the app from both gradle and bazel; then doing the "Order is Important" chapter from the story "Ratios: Part 1".

[adhiamboperes]

Thanks @masclot.

Since we don't have automated tests for these assets, what you can do is add before/after videos and screenshots. If you check out this branch, a video recording should show that the bug does not occur, and a logcat screenshot should show the stacktrace is not logged. Similarly, if you check out develop, the original bug and error log should be seen in the video and screenshot. Please add these to your PR description and reassign once done.

[masclot]

Thanks @masclot.

Since we don't have automated tests for these assets, what you can do is add before/after videos and screenshots. If you check out this branch, a video recording should show that the bug does not occur, and a logcat screenshot should show the stacktrace is not logged. Similarly, if you check out develop, the original bug and error log should be seen in the video and screenshot. Please add these to your PR description and reassign once done.

Done. PTAL @adhiamboperes

[adhiamboperes]

LGTM, thanks @masclot!

[oppiabot]

Unassigning @adhiamboperes since they have already approved the PR.

[oppiabot]

Assigning @BenHenning for code owner reviews. Thanks!

[BenHenning]

Thanks @masclot! This LGTM.

[BenHenning]

Restarting failing CI (since it appears to be an infrastructure flake) and enabling auto-merge.

[oppiabot]

Unassigning @BenHenning since they have already approved the PR.

[oppiabot]

Hi @masclot, this PR is ready to be merged. Please address any remaining comments prior to merging, and feel free to ask someone to merge your PR once the CI checks pass and you're happy with it. Thanks!