feat: Establish simple CLI for serving user code

[grypez]

Closes #233

Adds the new @ocap/cli package and includes an ocap binary in the monorepo top level.

ocap bundle

Use the endo bundler to prepare the given .js file, or every .js file in the given directory.

$ yarn ocap bundle packages/extension/src/vats/
> bundling dir ~/ocap-kernel/packages/extension/src/vats
> ~/ocap-kernel/packages/extension/src/vats/sample-vat.js
> wrote ~/ocap-kernel/packages/extension/src/vats/sample-vat.bundle: 2552 bytes

ocap serve

Serve .bundle files from the given directory, addressed relative to the directory.

$ yarn ocap serve packages/extension/src/vats/
> serving packages/extension/src/vats/ on localhost:3000

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/serve-handler@6.1.4	None	+2	2.12 MB	types
npm/@types/yargs@17.0.33	None	+1	69.1 kB	types
npm/serve-handler@6.1.6	environment, filesystem	+7	292 kB	vercel-release-bot

View full report↗︎

[rekmarks]

Nice! See inline comments for various suggestions.

[rekmarks]

In addition, the package should be added to the root tsconfig.json references field. If the package is built using ts-bridge (which I'm not sure should be the case), it should also be added to the root tsconfig.build.json. As long as we can build the CLI via yarn build and the run commands using yarn ocap <command>, we're good.

[sirtimid]

@grypez can you also fix the E2E test workflow and the start:server command which is used in the playwright config?

[grypez]

@grypez can you also fix the E2E test workflow and the start:server command which is used in the playwright config?

moved to #265

stale

[rekmarks]

LGTM!