fix: kickOut takes a reason error rather than a message string

[erights]

Prior to this PR we have the following line of code:

throw zcfSeat.kickOut(err.message);

The problem with this pattern of code is that err had an associated stack trace, whereas err.message is just a string. Currently we're not doing anything to correlate stack traces of sent errors with received errors, but I'm hoping to change that. This PR is in anticipation of that change.

I adopt the naming convention associated with a promise's rejection reason, which is normally an error object, of calling it a reason. I change kickOut to accept such a reason error rather than a message string. I fix the types, including noticing and fixing a bug in the notifier's type of updater.fail. This was declared with the same T template variable as for the values being reported, which was always wrong. It is now specifically a reason: Error.

Where the zcfSeat does an eventual send of kickOut to the zoeSeat, it also hardens the reason. The marshal layer transmits simple hardened errors. The marshal layer currently does not to enable recovery of the stack, but that's where I'm going.

This came up when @michaelfig and I were working on upgrading pegasus to the new Zoe.

[michaelfig]

I think reason should be typed as any, just as Promise.reject.

[katelynsills]

looks good!