Better UX for RequestError

[BTWS2]

This approach guides the users to the solution, without leaving VS Code:

1. Shows the error and shows the solution with a button. Don't solve automatically because user needs to know a setting will change to solve the error.
   
2. Setting is shown to user. The blue bar shows the setting has changed.
3. Info message tells user the setting changed. Refresh treeview to show everything works now.
   

Closes #363.

[codecov]

Codecov Report

Merging #375 (149600d) into master (9a93f4c) will decrease coverage by 0.57%.
The diff coverage is 27.27%.

@@            Coverage Diff             @@
##           master     #375      +/-   ##
==========================================
- Coverage   53.21%   52.64%   -0.58%     
==========================================
  Files          34       34              
  Lines         560      568       +8     
  Branches       96       98       +2     
==========================================
+ Hits          298      299       +1     
- Misses        231      238       +7     
  Partials       31       31              

Flag	Coverage Δ
integration	52.11% <27.27%> (-0.57%)	⬇️
unit	75.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/api/client.ts	62.74% <20.00%> (-9.99%)	⬇️
src/constants/actions.ts	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9a93f4c...149600d. Read the comment docs.

[thepieterdc]

I will modify this PR tomorrow to execute this logic in the error handler; so that the user does not have to deal with this themselves.