fix(daemon,cli): Fix #2700 use endo/init to prepare async hooks (#2708)

Closes: #2700
Refs: #2701

## Description

Implements exactly @mhofman 's suggestion at
#2700 (comment)

Alternative to #2701 

Changes some occurrences of `import 'ses';` to `import '@endo/init';` so
that the async hooks are properly prepared so that things work in an
interactive debug session -- at least in vscode. See #2700

However, there are many other bare `import 'ses';` occurrences in endo.
How many for of these need to `import '@endo/init';` instead in order to
avoid this same problem? For now, I conservatively looked for other
occurrences of the common marking comment "Establish a perimeter". I
found two additional ones that this PR currently just annotates with a
TODO. ***Reviewers, please advise.***

If we take this approach, can we avoid needing to teach developers not
to `import 'ses';` so they avoid this problem? Or should we move the
async-hook preparation somehow from `@endo/init` in `ses`, perhaps as a
repair, so all existing `import 'ses';` occurrences become correct?

Or should we instead proceed with #2701 after all?


### Security Considerations

none

### Scaling Considerations

none

### Documentation Considerations

Weird to need to teach developers to avoid `import 'ses';`. I hope we
can avoid needing to teach this. ***Reviewers*** please advise.

### Testing Considerations

The underlying issue #2700 occurs during an interactive debug session.
If this is not fixed, it can impede the run-debug-loop, especially for
running tests. In particular, ses-ava currently `import 'ses';` rather
than `import '@endo/init';`. This would perhaps be the highest next
priority to change.

### Compatibility Considerations

Perhaps not all occurrences of `import 'ses';` can or should be switched
to `import '@endo/init';` because of the other things bundled into
`@endo/init`.

### Upgrade Considerations

I think none. ***Reviewers: please double check me on this.***

Author: kriskowal

packages/cli/package.json

@@ -39,6 +39,7 @@
     "@endo/exo": "workspace:^",
     "@endo/far": "workspace:^",
     "@endo/import-bundle": "workspace:^",
+    "@endo/init": "workspace:^",
     "@endo/lockdown": "workspace:^",
     "@endo/pass-style": "workspace:^",
     "@endo/patterns": "workspace:^",

packages/cli/src/endo.js

@@ -3,9 +3,7 @@
 /* eslint-disable no-await-in-loop, no-bitwise, no-throw-literal */
 
 // Establish a perimeter:
-import 'ses';
-import '@endo/eventual-send/shim.js';
-import '@endo/lockdown/commit.js';
+import '@endo/init';
 
 import fs from 'fs';
 import url from 'url';

packages/daemon/src/daemon-node.js

@@ -2,10 +2,7 @@
 /* global process */
 
 // Establish a perimeter:
-import 'ses';
-import '@endo/eventual-send/shim.js';
-import '@endo/promise-kit/shim.js';
-import '@endo/lockdown/commit.js';
+import '@endo/init';
 
 import crypto from 'crypto';
 import net from 'net';

packages/daemon/src/worker-node.js

@@ -2,10 +2,7 @@
 /* global process */
 
 // Establish a perimeter:
-import 'ses';
-import '@endo/eventual-send/shim.js';
-import '@endo/promise-kit/shim.js';
-import '@endo/lockdown/commit.js';
+import '@endo/init';
 
 import fs from 'fs';
 import url from 'url';

packages/daemon/test/endo.test.js

@@ -2,9 +2,7 @@
 /* global process */
 
 // Establish a perimeter:
-import 'ses';
-import '@endo/eventual-send/shim.js';
-import '@endo/lockdown/commit-debug.js';
+import '@endo/init/debug.js';
 
 import test from 'ava';
 import url from 'url';

yarn.lock

@@ -374,6 +374,7 @@ __metadata:
     "@endo/exo": "workspace:^"
     "@endo/far": "workspace:^"
     "@endo/import-bundle": "workspace:^"
+    "@endo/init": "workspace:^"
     "@endo/lockdown": "workspace:^"
     "@endo/pass-style": "workspace:^"
     "@endo/patterns": "workspace:^"