REST API: swagger / OPEN-API documentation and UI

[jbride]

Implement in mujina using the following dependencies:

• utoipa = { version = "5.3", features = ["axum_extras"] }
• utoipa-swagger-ui = { version = "8.1", features = ["axum"] }

[rkuester]

Hey Jeff, thank you for being patient while, as we discussed in person, I reorganized and pushed some of the API work I had already started so that we had a baseline from which to start. I've pushed those commits to main now as of fb9fb9b.

The API loosely documented in docs/api.md, and you can poke at the Swagger UI at /swagger-ui if you run the daemon. A couple things worth pointing out: the API is organized around a full miner state tree (GET /api/v0/miner) with filtered sub-tree views for boards and sources, and write operations typically use PATCH on the parent resource rather than per-action endpoints. This is slightly different from what you proposed but the docs and code should lay out idea. The board listing (#18) is there, including the temp and fan data you mentioned in your follow-up. The command channel infrastructure (#15) is in place with a MPSC + oneshot, just like you proposed. OpenAPI and Swagger UI (#17) are wired up with the utoipa stack as you suggested. Analogs to the per-board write operations (voltage #19, frequency #21, fan speed #22) aren't implemented yet, but the plumbing is started to support them. The PATCH method on /miner is the pattern I was envisioning. Reinitialize (#16) might be an example of something that does deserve to be an action-oriented, POST endpoint.

Definitely think of what I've pushed as a starting point rather than a finished design. I'm gonna step back now and let you guys drive this forward using the Bitaxe board as a use case. I'll be working on the EmberOne/00 board's integration as I bring that board up further. Would be great to compare notes as we go.