improve: anyware builder

[jasonkuhrt]

progresses #1236

[jasonkuhrt]

Update:

I have gotten types passing.

I need now to fill in implementation.

It should be minimal effort because the runtime of anyware has essentially not been touched.

It should be just a matter of wiring a few function inputs to the pipeline type.

One unresolved maybe issue is how return errors type has broken. It has gone from union of ContextualError|DOMException to ContextualErrorAggregate. This may be an acceptable loss to keep momentum going, and keeping in mind the entire outputs system is generally in need an of an iteration (for example the input config for it).

Recapping the priorities:

• Get this merged
• Anyware gains a concept of pipeline context data, not tied to input or output of any one hook. How to make this available to interceptors requires some thinking:
  • union types of input that branch on context conditions
  • context spans all hooks so should it come from top level parameter? but then how to reconcile with above point?
• Anyware gains an ability to have extensions that can:
  • extend the context type
  • extend hook input/ouput types
  • provide a runtime for 1 or more hooks
  • declare a context-condition (e.g. use me when context data has transport=http)

This PR has focused on reworking the Anyware interface to something clean enough to pursue the significant challenge above.