Zarf tools update-creds errors when updating internal git or artifact server when it doesn't exist

[AustinAbro321]

Environment

App version: v0.38.2 (though the issue may have been introduced earlier)

Steps to reproduce

1. zarf init --confirm (no git server deployed)
2. zarf tools update-creds

Expected result

Update creds successfully

Actual Result

Fails because Zarf tries to login to the git server to generate a new artifact token, but the git server doesn't exist.

Temporary workaround

Update creds one at a time. For example if you only need to update the registry creds and the state in the agent run

zarf tools update-creds registry
zarf tools update-creds agent

Note

The underlying issue here is that we save state for git servers and artifact servers even when they don't exist, but we should create a fix for this in the short term. This is related to #2740