Staged on #2419 

Closes: #XXXX
Refs: #2414 #2418 #2419 

## Description

#2414  by itself does not work on Node 18 and Node 20 because
- those platforms do not have `Array.prototype.transfer`, so #2414 must
use `structuredClone` instead
- `structuredClone` does exist on Node >= 18, so it should be on
supported platforms (though see #2418 ). However, `structuredClone`
itself is dangerous and so must not be added to the shared intrinsics.
As a result, in #2414 , when `@endo/pass-style` is initialized in a
created compartment, it fails to find either `Array.prototype.transfer`
and `structuredClone

To solve this, @kriskowal suggested that we also shim
`Array.prototype.transfer` if needed during `lockdown`, along with other
repairs. We are avoiding similarly shimming
`Array.prototype.transferToImmutable` because it is not yet standard.
But `Array.prototype.transfer` is standard, and so `lockdown` can
globally shim it before hardening the shared intrinsics.

This PR implements @kriskowal 's suggestion.

### Security Considerations

none
### Scaling Considerations

by itself, none
### Documentation Considerations

nothing signicant.
### Testing Considerations

See #2418 . Aside from that, none
### Compatibility and Upgrade Considerations

On platforms with neither `Array.prototype.transfer` nor a global
`structuredClone`, the ses-shim will *currently* not install an
emulation of `Array.prototype.transfer`. However, once we verify that
endo is not intended to support platforms without both, we may change
lockdown to throw, failing to lock down.

Closes: #XXXX
Refs: 
- ocapn/ocapn#125 
-
https://github.com/ocapn/ocapn/blob/28af626441da888c4a520309222e18266dd2f1f2/draft-specifications/Model.md
- #2452 
  - Agoric/agoric-sdk#10084 
- https://github.com/tc39/proposal-immutable-arraybuffer 
  - #2414

## Description

Revise Smallcaps cheatsheet to track OCapn as of
ocapn/ocapn#125

### Security Considerations

none

### Scaling Considerations

none

### Documentation Considerations

the point. The cheatsheet was becoming too stale.

### Testing Considerations

none

### Compatibility Considerations

none

### Upgrade Considerations

none

Closes: #1331 
Refs: ocapn/ocapn#5 (comment)
#2414

## Description

Recognize Immutable ArrayBuffers, when also frozen, as the new
pass-style `byteArray`. Add a branch for each of the dispatches on
pass-style that must now understand byte-arrays as well. As of this PR,
many of those additional branches are stubbed out with "not yet
implemented" errors as placeholders.

### Security Considerations

The underlying shim implementation, if we're still using that, uses a
normal mutable ArrayBuffer internally, but safely encapsulates it so
nothing outside the shim can mutate it.

### Scaling Considerations

The underlying shim implementation helps us handle bulk binary data in a
largely no-copy or minimal-copy manner.

### Documentation Considerations

Will add a new pass-style, so everywhere we enumerate all the
pass-styles, we'll need to add byte-array.

### Testing Considerations

- [ ] TODO tests. For each stubbed out case, there instead should be a
`test.failing` test.

### Compatibility Considerations

Old code that dispatched only on the pass-styles it knew about will not
correctly handle passables that contain byte-arrays.

The shim cannot reasonably support TypedArrays of DataViews backed by
Immutable ArrayBuffers.

### Upgrade Considerations

- [ ] TODO BREAKING.md
- [ ] TODO NEWS.md

Closes: #1331 
Refs: ocapn/ocapn#5 (comment)
#2414

## Description

Recognize Immutable ArrayBuffers, when also frozen, as the new
pass-style `byteArray`. Add a branch for each of the dispatches on
pass-style that must now understand byte-arrays as well. As of this PR,
many of those additional branches are stubbed out with "not yet
implemented" errors as placeholders.

### Security Considerations

The underlying shim implementation, if we're still using that, uses a
normal mutable ArrayBuffer internally, but safely encapsulates it so
nothing outside the shim can mutate it.

### Scaling Considerations

The underlying shim implementation helps us handle bulk binary data in a
largely no-copy or minimal-copy manner.

### Documentation Considerations

Will add a new pass-style, so everywhere we enumerate all the
pass-styles, we'll need to add byte-array.

### Testing Considerations

- [ ] TODO tests. For each stubbed out case, there instead should be a
`test.failing` test.

### Compatibility Considerations

Old code that dispatched only on the pass-styles it knew about will not
correctly handle passables that contain byte-arrays.

The shim cannot reasonably support TypedArrays of DataViews backed by
Immutable ArrayBuffers.

### Upgrade Considerations

- [ ] TODO BREAKING.md
- [ ] TODO NEWS.md