improve sentry error reporting to include metadata about steps the transaction controller has taken

it could be helpful to see in what case something could be asking for a txMeta that the tx-state-manager dosen't have...

recording the history of the txController and what methods were called and where it was initiated from may help with this

reasons for doing this:

https://sentry.io/organizations/metamask/issues/754048659/?project=273505&query=is%3Aunresolved&statsPeriod=14d&utc=false

Start by tracing the transaction controller and tx-state-manager paths involved when txMeta is requested, then review the linked Sentry issue for the failure context. Determine where Sentry errors are assembled and what controller history and initiation details are available; done means the reports expose enough transaction-controller context to diagnose missing txMeta cases.

Written by the indexing model from the issue text.