feat: Add Base to Smart Transaction supported chains

[httpJunkie]

Description

What is the reason for the change?

Smart Transactions are currently supported on Ethereum Mainnet and BNB Smart Chain, but not on Base. As part of our effort to expand Smart Transactions functionality to more networks, Base needs to be added to the list of supported chains.

What is the improvement/solution?

This PR adds Base to the list of supported chains for Smart Transactions in the extension by:

• Adding CHAIN_IDS.BASE to ALLOWED_SMART_TRANSACTIONS_CHAIN_IDS_DEVELOPMENT
• Adding CHAIN_IDS.BASE to ALLOWED_SMART_TRANSACTIONS_CHAIN_IDS_PRODUCTION
• Updating tests to include Base in the expected supported chains list

These changes allow the extension to recognize Base as a valid network for Smart Transactions, enabling users to benefit from Smart Transactions functionality when interacting with the Base network.

Related issues

Fixes: TXL-697 TXL-699

Manual testing steps

Since Base isn't supported yet and this PR simply adds Base to list of supported chains, we are not testing Base/STX functionality yet, but ensuring that existing functionality remains intact.

This PR updates the version of @metamask/smart-transactions-controller, confirm that it doesn't break anything. Manual testing included:

• Verifying STX still works correctly on Ethereum Mainnet (see screenshot image)
• Checking that network switching between supported networks maintains proper STX state
• Ensuring STX settings UI correctly displays supported networks
• Confirming swap transactions with STX enabled complete successfully
• Ensuring that STX Description in Advanced Settings is correctly updated (see before/after images)

Screenshots/Recordings

Before

After

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.

[httpJunkie]

I have read the CLA Document and I hereby sign the CLA

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud