feat: add uds ui cmd

[decleaver]

Description

Adds uds ui which launches uds runtime

Related Issue

Relates to #870

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed

[UncleGedd]

Can we get around having to add the binaries to the repo? Also we shouldn't need to bundle all versions of Runtime into the binary. For example the darwin-arm64 CLI should embed only the darwin-arm64 Runtime. Thoughts?

[decleaver]

Can we get around having to add the binaries to the repo? Also we shouldn't need to bundle all versions of Runtime into the binary. For example the darwin-arm64 CLI should embed only the darwin-arm64 Runtime. Thoughts?

Good point, I can update it to only bundle the matching runtime binary. As far as adding the binaries to the repo, have some thoughts... pros/cons to different approaches.

[UncleGedd]

Great work! I explored vendoring for a bit before realizing that was a dead end. One con to the embedding binary approach is that we're creating tmp dirs with the runtime binary on the user's system, and those tmp dirs can potentially be abandoned if the process is killed and the defer function doesn't get called (like when the user runs ctrl-c)

This can be a separate issue, but I'd like to see the following scenarios handled:

1. What happens when the user hits ctrl-c? Can we force a cleanup of the tmp dir?
2. Besides ctrl-c is there a graceful way to exit uds ui?

[decleaver]

• What happens when the user hits ctrl-c? Can we force a cleanup of the tmp dir?
• Besides ctrl-c is there a graceful way to exit uds ui?

Created follow on issue: #922