Add lightweight netlab API server command

[captainpacket]

Adds a minimal netlab API server (stdlib HTTP) to expose CLI actions for automation. Includes new CLI command, help listing, and docs page.

[captainpacket]

This is primarily an automation I built to hook netlab into Semaphore UI

[DanPartelly]

Thank you ! I certainly see some future in this.

Could you please write some words describing the problem you are trying to solve with this commit? So we can start from a common understanding?

[captainpacket]

Engineers here need to model and test lots of different vendors and networks. We've had some internal tooling in the past to do this manually (some hack expect style scripts), but have switched to netlab to make the environment a bit more composable.

We started using Semaphore UI (https://semaphoreui.com/) as a job execution engine, which works well with the built in terraform/ansible worklows in a multi-user environment. It can also do manual bash/python scripts. I'd started with bash scripts with sshpass, but found them kinda brittle. I wanted to switch to an API based workflow to make it a bit more robust.

I'd initially wrote a FastAPI based wrapper that imports these functions (which I'm still using), but I had the thought that this could be easily extended in the native CLI workflow. A typed version I think still has use and this could be extended for that.

[ipspace]

@captainpacket -- Thanks a million for the PR. Definitely an interesting idea ;) and I truly appreciate you crossing all the Ts and dotting all the Is.

Give me a few days -- I'm stuck in the "we have to deal with another Ansible brokenness" bog, and have to get out of that first.

[captainpacket]

Cleaned up a few semaphore specific things (project/task) that I'd left behind; added minimal authentication and TLS option

[ipspace]

Mostly minor details and improvement suggestions, the only showstopper is whether jobs can be run in parallel and how to handle that.

[ipspace]

Looks good to me. Thank you & welcome to the club ;)

[ipspace]

@captainpacket -- Looks like you overcomplicated typing definitions and made mypy unhappy (CI check has failed). It could be a real mismatch (in which case it needs to be fixed), or just a confusing type (I would something go just with typing.List or typing.Callable without specifying the details).

[captainpacket]

@captainpacket -- Looks like you overcomplicated typing definitions and made mypy unhappy (CI check has failed). It could be a real mismatch (in which case it needs to be fixed), or just a confusing type (I would something go just with typing.List or typing.Callable without specifying the details).

Ahh yeah - I overspecified the typing a bit. I loosened it up and mypy passes locally.