Expose full wrapped ZCF to orchestrated flows

[mhofman]

What is the Problem Being Solved?

ZCF has some methods that are not currently compatible with the async-flow membrane, even if it had E support. It's mostly due to a nested promise in the result of makeEmptySeatKit.

We'll be working around this by simply removing support for some aspects of ZCF (#9773), but a fuller feature set is necessary for some use cases like vaults orchestration.

Description of the Design

Updated endowed wrapper for ZCF (see #9823) with more methods supported. Possibly requires a wrapper for userSeat.

Orchestration friendly versions of offerTo as an endowment. Possibly requires a wrapper / attenuation of zoeService, or some entanglement with the ZCF wrapper.

These may need a working retrySend implementation on the host side. See #9608 and #9541

Security Considerations

None

Scaling Considerations

Should be none

Test Plan

TBD

Upgrade Considerations

Exposing more methods on the wrapper should not affect existing flow activations unless they feature test for the presence of methods, which we currently do not recommend with some async-flow support for behavior changes across upgrades.