[SCP] Fine-grained failure reasons in thesky check for SCP

[romilbhardwaj]

Current output if ~/.scp/scp_credential does not exist:

  SCP: disabled
    Reason: Failed to access SCP with credentials. To configure credentials, see: https://cloud.samsungsds.com/openapiguide
    Generate API key and add the following line to ~/.scp/scp_credential:
      access_key = [YOUR API ACCESS KEY]
      secret_key = [YOUR API SECRET KEY]
      project_id = [YOUR PROJECT ID]

If I don't have a ~/.scp/scp_credential file, the Reason message on sky check should be descriptive and tell me exactly that file does not exist. Similarly, if the credentials are incorrect, we should re-word this to say credentials are invalid.

We should catch each exception here separately and print out nice reasons on how to fix:

skypilot/sky/clouds/scp.py

Lines 285 to 293 in d022512

	except (AssertionError, KeyError, scp_utils.SCPClientError):
	return False, ('Failed to access SCP with credentials. '
	'To configure credentials, go to:\n'
	' https://cloud.samsungsds.com/openapiguide\n'
	' to generate API key and add the line\n'
	' access_key = [YOUR API ACCESS KEY]\n'
	' secret_key = [YOUR API SECRET KEY]\n'
	' project_id = [YOUR PROJECT ID]\n'
	' to ~/.scp/scp_credential')

The R2 check implementation may be a good reference.

[ksasi]

We see similar output even for Lambda

Lambda: disabled
    Reason: Failed to access Lambda Cloud with credentials. To configure credentials, go to:
      https://cloud.lambdalabs.com/api-keys
    to generate API key and add the line
      api_key = [YOUR API KEY]
    to ~/.lambda_cloud/lambda_keys

[github-actions]

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[github-actions]

This issue was closed because it has been stalled for 10 days with no activity.