[Refactor] Replace getText() with findElement using css

[DDDDDanica]

After a few fixes for flaky tests in MV3, it is noticeable that lots are related to an assertion pattern change, which is to find an element, then assert what its contents are. There's a racing condition in some e2e tests to find the dom and assert, and we'll try to avoid this pattern.

Proposed by Mark in this thread

e.g. Instead of this:

const element = await driver.findElement('[data-testid="foo"]');
assert(await element.getText(), 'Bar')

Do this:

await driver.findElement({
  css: '[data-testid="foo"]',
  text: 'Bar',
});

Hence, we want to introduce an new lint rules to forbid this pattern from being written;
Also refactor all existing places we used this pattern to reduce the noise if monitoring MV3 e2e tests.

Acceptance criteria:

1. lint error for using findElement and getText when comes to comparing element text and string
2. all existing tests use new findElement pattern.

[seaona]

This will need several PRs as there are lots of occurrences. I'll update the status in this comment:

• first PR is here test: removing race condition for asserting inner values (PR-#1) #27606
• second PR is here test: removing race condition for asserting inner values (PR-#2) #27664
• another PR fix: flaky test ERC1155 NFTs testdapp interaction should batch transfers ERC1155 token #27897
• another PR fix: flaky test ERC721 NFTs testdapp interaction should prompt users to add their NFTs to their wallet (all at once) #27889
• another PR fix: flaky anti-pattern getText + assert #28041
• another PR fix: flaky anti-pattern getText + assert 2 #28043
• another PR fix: flaky anti-pattern getText + assert 3 #28062

[seaona]

I re-open the issue, since we'll need several PRs to fix all occurrences. So far we merged 1