test: remove toMatchSnapshot and removed snapshot files in confirmations tests (#29287)

<!--
Please submit this PR as a draft initially.

Do not mark it as "Ready for review" until this PR meets the canonical
Definition of Ready For Review in `docs/readme/ready-for-review.md`.

In short: the template must be materially complete (not just section
titles
present), all status checks must be currently passing, and the only
expected
follow-up commits must be reviewer-driven.
-->

## **Description**

> Refactors confirmations-related unit tests to stop using
toMatchSnapshot and instead assert on specific UI elements via
@testing-library/react-native (e.g., presence of buttons, text, and
testIDs) across Tooltip, BottomModal, CopyButton, Network,
BlockaidBanner, AddressElement/List, approval templates/results, and
transaction header.
> 
> Deletes the associated Jest snapshot files and adds a testID
(blockaid-banner-loader) to the BlockaidBanner ActivityIndicator so the
loader state can be asserted without snapshots.

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry:

## **Related issues**

Fixes:

## **Manual testing steps**

```gherkin
Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]
```

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] 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](https://jsdoc.app/) format
if applicable
- [ ] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [ ] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [ ] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [ ] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] 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.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk: changes are confined to test expectations and snapshot
removals, with only a minor UI change adding a `testID` to the Blockaid
loader for testability.
> 
> **Overview**
> Refactors confirmations-related unit tests to **stop using
`toMatchSnapshot`** and instead assert on specific UI elements via
`@testing-library/react-native` (e.g., presence of buttons, text, and
testIDs) across Tooltip, BottomModal, CopyButton, Network,
BlockaidBanner, AddressElement/List, approval templates/results, and
transaction header.
> 
> Deletes the associated Jest snapshot files and adds a `testID`
(`blockaid-banner-loader`) to the BlockaidBanner `ActivityIndicator` so
the loader state can be asserted without snapshots.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
0d0a988. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: cortisiko

app/components/Views/confirmations/components/UI/Tooltip/Tooltip.test.tsx

@@ -5,18 +5,19 @@ import { fireEvent, render } from '@testing-library/react-native';
 import Tooltip from './Tooltip';
 
 describe('Tooltip', () => {
-  it('should match snapshot', async () => {
-    const container = render(
+  it('renders the open button', () => {
+    const { getByTestId } = render(
       <Tooltip
         title="Tooltip title"
         content={
           <View>
             <Text>Tooltip content to be displayed here!</Text>
           </View>
         }
+        tooltipTestId="tooltipTestId"
       />,
     );
-    expect(container).toMatchSnapshot();
+    expect(getByTestId('tooltipTestId-open-btn')).toBeOnTheScreen();
   });
 
   it('should display content when info icon is clicked', async () => {
@@ -34,7 +35,9 @@ describe('Tooltip', () => {
       />,
     );
     fireEvent.press(getByTestId('tooltipTestId-open-btn'));
-    expect(getByText('Tooltip content to be displayed here!')).toBeDefined();
+    expect(
+      getByText('Tooltip content to be displayed here!'),
+    ).toBeOnTheScreen();
     expect(mockOnPress).toHaveBeenCalled();
   });
 });

app/components/Views/confirmations/components/UI/Tooltip/__snapshots__/Tooltip.test.tsx.snap

@@ -5,15 +5,15 @@ import renderWithProvider from '../../../../../../util/test/renderWithProvider';
 import BottomModal from '.';
 
 describe('BottomModal', () => {
-  it('should match snapshot', async () => {
-    const container = renderWithProvider(
+  it('renders children', () => {
+    const { getByText } = renderWithProvider(
       <BottomModal>
         <View>
           <Text>DUMMY</Text>
         </View>
       </BottomModal>,
       { state: {} },
     );
-    expect(container).toMatchSnapshot();
+    expect(getByText('DUMMY')).toBeOnTheScreen();
   });
 });

app/components/Views/confirmations/components/UI/bottom-modal/__snapshots__/bottom-modal.test.tsx.snap

@@ -9,9 +9,9 @@ jest.mock('../../../../../../core/ClipboardManager', () => ({
 }));
 
 describe('CopyButton', () => {
-  it('should match snapshot', async () => {
-    const container = render(<CopyButton copyText={'DUMMY'} />);
-    expect(container).toMatchSnapshot();
+  it('renders the copy button', () => {
+    const { getByTestId } = render(<CopyButton copyText={'DUMMY'} />);
+    expect(getByTestId('copyButtonTestId')).toBeOnTheScreen();
   });
 
   it('should copy text to clipboard when pressed', async () => {

app/components/Views/confirmations/components/UI/bottom-modal/bottom-modal.test.tsx

@@ -23,11 +23,11 @@ const mockInitialState = {
 };
 
 describe('Network', () => {
-  it('should match snapshot', async () => {
-    const container = renderWithProvider(
+  it('renders the network avatar', () => {
+    const { getByTestId } = renderWithProvider(
       <Network chainId={CHAIN_IDS.MAINNET} />,
       { state: mockInitialState },
     );
-    expect(container).toMatchSnapshot();
+    expect(getByTestId('network-avatar-image')).toBeOnTheScreen();
   });
 });