refactor: kill extrinsic errors, use metadata error matching instead

[rflechtner]

fixes KILTProtocol/ticket#1652

This makes use of module error matching based on chain metadata info.
Our internal extrinsic error matching is removed.
Minor changes necessary to get this done relate to the recovery by resign functionality, and the SubscriptionPromise maker.

How to test:

test & integration tests suffice

Checklist:

• I have verified that the code works
• I have verified that the code is easy to understand
  • If not, I have left a well-balanced amount of inline comments
• I have left the code in a better state
• I have documented the changes (where applicable)

[tjwelde]

That looks SO MUCH better!
Just some nitpicks

[rflechtner]

while working on this I wrote this little gadget which I had included in the ErrorHandler.ts but not committed (yet):

export function throwExtrinsicError(extrinsicResult: ISubmittableResult): void {
  const { dispatchError } = extrinsicResult
  if (!dispatchError) return
  if (dispatchError.isModule) {
    const moduleError = dispatchError.registry.findMetaError(
      dispatchError.asModule
    )
    const { section, index, name, docs } = moduleError
    throw new ExtrinsicError(
      `Module Error ${section}.${name}(${index}): ${docs.join(' ')}`
    )
  }
  if (dispatchError.isToken || dispatchError.isArithmetic) {
    throw new ExtrinsicError(
      `${dispatchError.type} Error: ${(dispatchError.value as TokenError).type}`
    )
  }
  throw new ExtrinsicError(`${dispatchError.type} Error`)
}

It's not used or needed anywhere, do you think that's something users would want to use?

[tjwelde]

Regarding #452 (comment):
Not sure about the usefullness. I imagine people will either want to show a generic message, when something goes wrong, or want to look at errors more in depth instead of just parsing an error message, if they want to handle something specific. I would leave it out of this PR.

[tjwelde]

LGTM