`azd up` logs show multiple CredentialUnavailable errors even during a successful run

## Issue

The output appears to show multiple errors or failures, even though the run is actually succeeding. This creates confusion and makes it difficult to distinguish real failures from normal fallback behavior. Users may assume something is broken when the workflow is functioning as intended.

Clearer logging or grouping could help users understand that the authentication fallback is expected behavior, not a failure.

## Observed Behavior

* Running `azd up` locally produces several error-looking messages from the credential chain before authentication succeeds.

* Example output:

```
EnvironmentCredential.get_token failed: EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
ManagedIdentityCredential authentication unavailable, no response from the IMDS endpoint.
SharedTokenCacheCredential authentication unavailable. No accounts were found in the cache.
AzureCliCredential.get_token succeeded
DefaultAzureCredential acquired a token from AzureCliCredential
Successfully connected to database
```

* Despite these error-like messages, the process completes normally:

```
Successfully connected to database
SQL Message: ... User already exists
Database user creation completed successfully
```