temp+fix: cp-7.60.1 bump bitcoin (#23488)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

Updates bitcoin to 1.8.0, which removes onRpcRequest method.

<!--
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?
2. What is the improvement/solution?
-->

## **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: Removed `onRpcRequest`
([#568](MetaMask/snap-bitcoin-wallet#568))

## **Related issues**

Fixes: Remove `onRpcRequest`.

## **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**

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

## **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.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Upgrade @metamask/bitcoin-wallet-snap from ^1.7.0 to ^1.8.0.
> 
> - **Dependencies**:
> - Upgrade `@metamask/bitcoin-wallet-snap` to `^1.8.0` in
`package.json`.
>   - Update `yarn.lock` to reflect the new version.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
6b5cf54. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: runway-github[bot]

.cursor/BUGBOT.md

@@ -6,18 +6,10 @@ Automated test quality enforcement and bug detection for MetaMask Mobile React N
 
 ## Execution Protocol
 
-### 1. Initial Setup - Unit Tests
+### 1. Initial Setup
 
 - **ALWAYS** load and reference [unit testing guidelines](rules/unit-testing-guidelines.mdc)
 - Verify test file naming pattern: `*.test.{ts,tsx,js,jsx}`
 - Check for proper Jest/React Native Testing Library imports
 
-Use the rules in the [unit testing guidelines](rules/unit-testing-guidelines.mdc) to enforce the test quality and bug detection.
-
-### 2. Initial Setup - E2E Tests
-
-- **ALWAYS** load and reference [e2e-testing-guidelines](rules/e2e-testing-guidelines.mdc)
-- Verify test file naming pattern: `e2e/specs/**/*.spec.{js,ts}`
-- Check for proper imports and framework utilities from `e2e/framework/index.ts`
-
-Use the rules in the [e2e-testing-guidelines](rules/e2e-testing-guidelines.mdc) to enforce the test quality and bug detection.
+Use the rules in the[unit testing guidelines](rules/unit-testing-guidelines.mdc) to enforce the test quality and bug detection.

.cursor/rules/component-view-testing.mdc

@@ -88,7 +88,7 @@ Use `.github/pull-request-template.md` - fill ALL sections:
   - Labels applied
 - Target `main` branch
 - Keep focused (single feature/fix)
-- Include tests (unit/Component-view/e2e)
+- Include tests (unit/integration/e2e)
 - Update TSDoc when relevant
 
 **⚠️ Force Push Policy**:

.cursor/rules/pr-creation-guidelines.mdc

@@ -1,4 +1,4 @@
-/* eslint-disable import/no-commonjs */
+// eslint-disable-next-line import/no-commonjs
 module.exports = {
   root: true,
   parser: '@typescript-eslint/parser',
@@ -147,20 +147,6 @@ module.exports = {
         },
       },
     },
-    {
-      files: ['**/*.view.test.{js,ts,tsx,jsx}'],
-      rules: {
-        'no-restricted-syntax': [
-          'error',
-          {
-            selector:
-              "CallExpression[callee.object.name='jest'][callee.property.name='mock'][arguments.0.type='Literal'][arguments.0.value!='../../../core/Engine'][arguments.0.value!='../../../core/Engine/Engine'][arguments.0.value!='react-native-device-info']",
-            message:
-              'Only Engine and react-native-device-info can be mocked in component-view tests.',
-          },
-        ],
-      },
-    },
   ],
 
   globals: {

.eslintrc.js

@@ -43,7 +43,6 @@ app/core/Engine/controllers/remote-feature-flag-controller/ @MetaMask/mobile-pla
 app/core/DeeplinkManager                                    @MetaMask/mobile-platform
 scripts/build.sh                                            @MetaMask/mobile-platform
 scripts/update-expo-channel.js                              @MetaMask/mobile-admins
-certs/certificate.pem                                       @MetaMask/mobile-admins
 
 # Platform & Snaps Code Fencing File
 metro.transform.js @MetaMask/mobile-platform @MetaMask/core-platform

.github/CODEOWNERS

@@ -66,18 +66,10 @@ body:
    id: version
    attributes:
      label: Version
-     description: What version of MetaMask are you running? You can find the version in "Settings" > "About MetaMask"
+     description: What version of MetaMask are you running? You can find the version in "Settings" > "About"
      placeholder: "7.50.0"
    validations:
      required: true
- - type: input
-   id: build-number
-   attributes:
-     label: Build number
-     description: What build number of MetaMask are you running? You can find the build number in "Settings" > "About MetaMask"
-     placeholder: "3055"
-   validations:
-     required: true
  - type: dropdown
    id: build
    attributes:

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -46,10 +46,8 @@ runs:
     - name: Fetch base branch for comparison
       shell: bash
       run: |
-        # Unshallow the repository first (if it's shallow)
-        git fetch --unshallow 2>/dev/null || true
-        # Then fetch base branch to ensure merge-base exists
-        git fetch origin main 2>/dev/null || true
+        # Fetch base branch with enough depth to compute merge base for git diff
+        git fetch origin main --depth=100 2>/dev/null || git fetch origin master --depth=100 2>/dev/null || true
 
     - name: Setup Node.js
       uses: actions/setup-node@v4

.github/actions/smart-e2e-selection/action.yml

@@ -19,6 +19,10 @@ The check can be bypassed when necessary, either by setting the changelog entry
 
 Any label can be manually added on demand depending on the PR's content. For instance, the label **QA passed** will indicate that a thorough manual testing has been performed and the PR is ready to be merged. In addition, following labels have some specific use cases.
 
+### Run Flask Android E2E tests
+
+- **run-android-flask-e2e-smoke**: The Android Flask E2E smoke tests jobs will run in the given PR. They also run on schedule on main branch.
+
 ### Bypass Quality Gates
 
 Using any of these labels should be exceptional in case of CI friction and urgencies. Please use them reasonably and verify new changes and regressions manually.