chore: refactor uds ui to use vendored runtime

[TristanHoladay]

Description

Refactors uds ui to vendor uds-runtime by downloading and embedding the Runtime UI release artifact and uds.dev certs. This means CLI will no longer have to download and include the Runtime binary.

Related Issue

https://github.com/defenseunicorns/uds-runtime/issues/417

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
• Contributor Guide Steps followed

[TristanHoladay]

@catsby some context / questions:

1. is it right to return an error from the cobra cmd here? i saw none of the other vendored commands were but the uds commands do.

2. Darcy had implemented handling for the interrupt signal and then cleaning up the temp files. since we don't need the temp files anymore i got rid of all that, but realized in the test that means we have to expect an Error when the interrupt occurs. Is that ok?

3. I thought it would be cleaner to have the build and cert assets under cmd/assets but because the fs.Sub() in the vendored Setup() is hardcoded to expect ui/build, it was unhappy with assets/ui/build. so i update the download script to place it all under cmd/.

[catsby]

LGTM; I'll sync up with you about question 2 as I'm not 100% sure which test you're talking about, it's not clear to me from these changes here. Question 1 and 3 seem fine to me.