[feature request] support plane/controller HTTP API

[HunterLarco]

In jamsocket/plane#434 the plane controller implemented an HTTP API to have (almost) parity with jamsocket. However, this package cannot be used with it for 2 reasons:

1. The initialization options (JamsocketInitOptions) require jamsocket account information which we don't have for a local plane deployment.
2. The pattern ${apiUrl}/user/${account}/service/${service}/spawn does not match ${apiUrl}/service/${service}/spawn exposed by the controller.

I imagine there are two reasonable solutions to this

1. JamsocketInitOptions should be a union type of either plane.dev connection options or jamsocket options.
2. The HTTP API exposed by the controller should match exactly the jamsocket API but treat the user information as no-op (or have auth values statically configured via the controller.conf)

I'm also sympathetic to the idea that plane.dev and jamsocket wont have parity because they are different! However, plane.dev makes a compelling local setup for anyone bringing their own compute, so ensuring that the rest of the jamsocket ecosystem plays nicely with plane.dev would be really really nice for making adoption easier.