Enable the ability to use the API to run containers disconnected but tracking

[tfoote]

This can build on #271 to keep track of containers and potentially kill them.

You can run them headless and then terminate them later for a background process.

Aka: Launch A non-ineteractive -> Launch B interactive --- B Finishes -> shutdown A.

[CodeVishal-17]

Hi, I’d like to work on this issue.

I’ve reviewed the description and the reference to #271, and I believe I understand the goal of enabling containers to run headlessly while still being tracked and terminated later through the API.

If no one else is currently working on this, I’d be happy to start working on an implementation. Please let me know if there are any design considerations I should be aware of before beginning.