Increase docker registry and git-server push fault-tolerance

[jeff-mccoy]

Description

This PR makes important changes to how the Zarf CLI interacts with a Docker Registry and Git Server during zarf package create operations. These changes were needed as some of the implementation details were related to legacy registry/git interactions from before v0.15.0:

• BREAKING CHANGE: No longer store credentials for docker or git locally to support changes/fixes below
• Dynamic local port binding for zarf connect git|logging|registry, this prevents issues where an existing binding is still open such as in CI/CD or when I user accidentally leaves a tunnel open in another terminal or background task. This is also part of the larger strategy for the utility cluster: If you need to interact with the cluster outside of Zarf or the in-cluster use by Zarf, then an ingress should be exposed.
• Remove docker-cli dependency that now seems to be breaking some systems where docker isn't running (even though the code should not directly depend on docker running
• Users that still want to use Zarf to log into a registry without docker can still use zarf tools registry login provided by Crane.

Related Issue

Fixes #515, #580
Related to #186

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist before merging

• Tests have been added/updated as necessary (add the needs-tests label)
• Documentation has been updated as necessary (add the needs-docs label)

[YrrepNoj]

I really like the usability of having the default connection commands using dynamic ports. Whoever came up with that had a really good idea 😉