orchestration: vow interface guard consistency

[0xpatrickdev]

What is the Problem Being Solved?

We use a mixture of VowShape and NetworkShape.Vow$ when defining interface guards for watchers in @agoric/orchestration. VowShape looks like:

M.tagged(
  'Vow',
  M.splitRecord({
    vowV0: M.remotable('VowV0'),
  }),
);

While NetworkShape.Vow$(shape) looks like M.or(shape, VowShape).

It’s debatable as to how much value NetworkShape.Vow$ buys us - it seems the .or for VowShape will always be the one hit - but in the course of #9449 it felt like a waste to remove shape’s that were previously working and provide helpful cues to the caller.

Description of the Design

1. Decide whether to use NetworkShape.Vow$, soon to be renamed to Vow$ and exported directly from @agoric/vow, or VowShape`.

2. Consistently implement the change in @agoric/orchestration exos, and only import type guard shapes for vows from @agoric/vow

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations