chore: Chore/9924 - Enable `@typescript-eslint/no-explicit-any` as error rule

[Cal-L]

Description

This PR adds the @typescript-eslint/no-explicit-any eslint rule to prevent the usage of any. Aside from adding the rule to eslintrc, all of the changes ignores the rule for existing usage of any

This is the mobile equivalent of https://github.com/MetaMask/metamask-extension/pull/23531/ for extension

Related issues

Fixes: #9924

Manual testing steps

• Run yarn lint
• Should not see errors about @typescript-eslint/no-explicit-any

Screenshots/Recordings

Before

After

No lint errors

Pre-merge author checklist

• [x] I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• [x] I've completed the PR template to the best of my ability
• [x] I’ve included tests if applicable
• [x] I’ve documented my code using JSDoc format if applicable
• [x] I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• [x] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• [x] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions[bot]]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions[bot]]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: c02c35265ab289ddf644c3f844b6a66994e4dbf5 Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1dfdc625-b627-48af-bce0-ec604d1ed813

[!NOTE]

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 40%)

See analysis details on SonarCloud

[Cal-L]

Quality Gate failed

Failed conditions 0.0% Coverage on New Code (required ≥ 40%)

See analysis details on SonarCloud

Since this PR only ignores the use of any, we will ignore/bypass SonarCloud coverage failure