If the 'external' git server still exists within the k8s cluster, create a tunnel when pushing repos to it

general cleanup and oranization of functions in hooks package for zarf agent

Makes sure the svc url comes at the end of the provided URL. This captures edge cases where someone has a subdomain that looks just like a service url would. eg) https://svc.cluster.local.example.com

update GitHub workflows to not explicitly create init-package if it's not needed (if it already exists)

The get-admin-password was a bad name because it wasn't clear what 'admin' meant. We are now making the name more explicit

update the flag git-username to git-account and add a note in the usage text to describe what to do if the repository belongs under an org

verify that the git-user and git-password has been provided if using an external git server

give users the ability to set some of the flags for the GitServerInfo without needing to host an extneral repository

ready check now verifies that the zarf-state has been loaded by verifying the distro field has been populated

instead of essentially hardcoding the container URL to be localhost:31999 we are now loading the containger registry information from the zarf state to get the address of the registry

instead of having a single 'secret' value and expanding that into other secrets for internal resources, we now store all the values necessary within the ZarfState

give users the ability to set some of the flags for the ContainerRegistryInfo without needing to host an external registry

instead of hardcoding the username for the gitea admin user we now template the value in the chart from the username stored in the ZarfState

… initialize flags

If a nodeport is provided, replaces the address with IPV4LocalHost

the utility function to create a read-only user to gitea was using hardcoded values for the push/read usernames. Now they check the gitServerInfo in the state to use the correct usernames

remove the hardcoded output for registry connect shortcut and only print if using an internal registry

instead of using the raw registry address, use the GetRegistry utility that checks if registry url should be modified to localhost

shortended getZarfStateFromWithinAgentPod() to getStateFromAgentPod()

add a flag that allows the user to specify the registry secrety, instead of using a randomly generated one

…uctions

When we are transforming repo URLs we used to replace invalid special characters from the url to double underscores. This created problems with some Git servers (namely GitLab) that prevents two special characters in a row.
Instead of replacing with double undersores, we are simply removing the invalid characters.

change the way we transform the git urls by only using the actual reponame and a sha of the url (exluding the tag in the sha)

…asum added

injector and agent components get processed before the zarf-agent is running, meaning there is nothing that rewrites the url to include the shasum when the chart is getting deployed. This means we need to push the images out without the shasum appended

…kflow

light cleanup of PR code

…unction

Have external test wait for registry and repository to be available b efore continuing with the test

…to-the-image-cache-directory

…to-the-image-cache-directory

…to-the-image-cache-directory

…to-the-image-cache-directory

…to-the-image-cache-directory