surface error message to users if plugin can't read aws/config file

[Will-ShaoHua]

Problem

When the plugin can't read config file (possible root cause is invalid format like space characters) or file R/W access), the login flow will return and we're not surfacing the error to users so that the login flow seems to be ir-responsive after users clicking login button.

#4509

Solution

surface the error to users

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Description

Checklist

• My code follows the code style of this project
• I have added tests to cover my changes
• A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
• I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
1.2% Duplication on New Code

See analysis details on SonarCloud

[Will-ShaoHua]

should figure out a better way to do this, maybe a toast notification, but will leave it as a followup