## **Description**

I'm working on Token sorting, and since I was in the area, I took the
opportunity to update the components I was touching to Typescript. This
PR handles those changes, and I'll work on the actual sorting logic in a
separate branch that I will merge with this one.

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/26952?quickstart=1)

## **Related issues**

First step of:
https://consensyssoftware.atlassian.net/browse/MMASSETS-356

## **Manual testing steps**

Nothing should be different visually or functionally. ~~I left a comment
on a suspicious snapshot test where I can't explain the diff, other than
the original snapshot not being accurate based on the mocks~~ 👈 no
longer relevant.

## **Screenshots/Recordings**

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [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](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.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.

---------

Co-authored-by: Brian Bergeron <[email protected]>

…7127)

## **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?
2. What is the improvement/solution?
-->
The asset picker in dark mode previously showed the down icon and token
symbol in their light mode variants, instead of dark mode. This is
because `Button` defaults to the primary variant which hard codes the
theme as light mode for all descendant elements. This PR changes the
AssetPicker main component from Button to ButtonBase since it does not
default to light mode

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/27127?quickstart=1)

## **Related issues**

Fixes: #27046 

## **Manual testing steps**

1. Change to dark mode
2. Open Send Page
3. Asset symbol and down carat should both render as white
4. Switch to light mode
5. Asset symbol and down carat should both render as black

## **Screenshots/Recordings**

### **Before**

<img width="1624" alt="image"
src="https://github.com/user-attachments/assets/69e086b1-daec-46d9-b299-74434d58a616">


### **After**

<img width="1624" alt="image"
src="https://github.com/user-attachments/assets/709898ae-9766-4902-a089-9183bac8fcc1">


## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [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](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
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.