fix: port uds-common/setup action

[catsby]

Description

Copy-over the now-removed uds-common/.github/actions/setup action into this repo. UDS Common was refactored and some actions were removed, so here we copy what this action was as of version v0.13.1 adopt the uds actions that are in uds-common now.

Original:

• https://github.com/defenseunicorns/uds-common/blob/v0.13.1/.github/actions/setup/action.yaml

In this lift-and-shift I replaced the steps for installing UDS CLI with the new, dedicated action for it at https://github.com/defenseunicorns/setup-uds.

Note: some of the inputs may not be relevant anymore, but I'm not entirely sure. Our usage supplies a username and password, but I don't see where the Action actually uses those, if at all. Additionally, I don't have the right access to see what secrets this repo (uds-k3d) has, so I don't what it might be putting in to the environment.

Related Issue

Relates to #116 which is a PR from Renovate that wont ever work because the latest versions of uds-common no longer have the referenced Action.

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

[rjferguson21]

So I'm catching up a bit with what changed in uds-common, but I think instead of adding a new setup action in this repo we should just try to consume the new actions tasks wherever possible.

For instance there is a task for authenticating with registries

You might not be able to go a step further and consume the callable workflows that are designed for uds-packages-* but it might end up being a better fit to just directly consume the uds tasks directly for this repo.

[catsby]

@rjferguson21 please take another look when you get the chance

[mjnagel]

Might be good to update the other locations this is called as well?

• https://github.com/defenseunicorns/uds-k3d/blob/build-test-setup-env-action/.github/workflows/tag-and-release.yaml#L35-L40
• https://github.com/defenseunicorns/uds-k3d/blob/build-test-setup-env-action/.github/workflows/publish-image.yaml#L28-L33 (this one is not currently in use)

[catsby]

@mjnagel that would indeed make sense 🤦‍♂️
I updated those as well. The setup-environment UDS Task should handle the Login to GHCR step we had here originally, so that should still be covered