Wallet unnecessarily tracks custom faucet accounts

### What should be done?

When fetching asset metadata from a faucet account, the wallet calls `importAccountById`, which stores the faucet account in the client db. That account remains tracked in the db, which can slow down state syncs and other operations.

### How should it be done?

Once the wallet stores the asset metadata, the faucet account can be untracked and removed from the client db. The web client may not currently expose the bindings to remove the account.

### When is this task done?

When faucet accounts are not tracked in the wallet persistently

### Additional context

_No response_

Find the code that fetches asset metadata from a faucet account, likely calling `importAccountById`. Examine the client database layer to understand how accounts are tracked and stored. Identify if bindings to remove an account exist in the web client; if not, they may need to be exposed. The task is done when faucet accounts are not persistently tracked after metadata retrieval.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.