chore: improving warnings on incorrect or absent configuration

[kieranmanning]

Still in progress

What?

Improve Cloudsmith CLI user experience when encountering configuration issues or uncertainties

Why?

Currently, there are a number of potential pitfalls around config management for the Cloudsmith CLI. These include:

1. No warnings when commands are passed non-existent profiles
2. No warnings when commands are run with zero discovered configuration
3. Normally remote commands appear to complete successfully despite not authenticating against, or reaching, any Cloudsmith instance

Acceptance Criteria (Is It Done?)

1. Incorrect --profile values result in warnings to users
2. The CLI expects to find some kind of accurate configuration and warns if not
3. Commands which expect API responses warn when none are returned, indicating likely authentication failure

Screenshots

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

• .envrc: Language not supported

[Copilot]

The word 'attemping' is misspelled. It should be 'attempting'.

Suggested change

	f"You're currently attemping to connect to Cloudsmith instance {cloudsmith_host}",
	f"You're currently attempting to connect to Cloudsmith instance {cloudsmith_host}",

[Copilot]

The variable 'repo' is assigned but never used. Consider removing it to clean up the code.