fix: Don't call WalletExport in msg signing flows

[magik6k]

Related Issues

Proposed Changes

Don't call WalletExport just to get key type

Additional Info

Calls to WalletExport breaks remote wallets, looks really bad in interactive wallets, and probably also breaks ledger wallet.

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[arajasek]

This doesn't work if the msg.From is an ID address, but looking at the code that case doesn't work anyway...

[magik6k]

I'm msg.From is resolved before we call into the wallet