refactor: snaps UI tests

[hmalik88]

Description

Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions:

1. What is the reason for the change? Currently, the snaps UI components tests are following varying patterns: tests in the component's folders (e.g. SnapUIInput), tests using renderInterface in SnapUIRenderer.test.tsx and then individual tests within the components subfolder that test the respective template mapper.
2. What is the improvement/solution? Make renderInterface re-usable and follow the testing pattern being used in the extension with tests using renderInterface e.g. input.test.ts. Using renderInterface we essentially test the component from mapping to rendering. This PR moves existing tests in "SnapUI" prefixed folders that do not have a corresponding test in the components subfolder. It also moves out some tests from SnapUIRenderer.test.tsx into their own files, similar to how we did in the extension.

Note: A subsequent PR will be opened to convert existing tests within the components subfolder to the renderInterface format and migrate any remaining "SnapUI" prefixed tests.

Related issues

Fixes: #14531

Pre-merge author checklist

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

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• 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]

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.

[Daniel-Cross]

Looks good to me!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
97.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud