Update Pinning operations and error messaging for Dev Box

[bbonaby]

Summary of the pull request

Note: Secondary PR in Dev Home repository: microsoft/devhome#2907

This PR makes sure that the pinning operation and errors are reflected in Dev Home. Currently When a pinning operation happens there is no status updates. Dev Home expects for every operation that the Compute System supports that there be a status update to inform the user something is occuring. E.g "Starting".

Things this PR updates:

1. updates the supported operations for Dev Boxes based on the state.
2. Updates the error messages and points the user to the azure extension logs
3. Updates the "DoPinActionAsync" and "GetPinStatusAsync" methods to be within a try/catch.
4. Remove the async void and used async task in the LoadWindowsAppParameters method as it was causing the Dev Boxes to randomly not contain the required WindowsAppParameters by the time Dev Home called the GetPinStatusAsync.

Video showing me performing the pinning and unpinning operations:

pinned.to.start.operations.updating.mp4

References and relevant issues

Detailed description of the pull request / Additional comments

Note: Due to the asynchrous calls for GetPinStatusAsync, when the operation to pin/upin the dev box is completed, the pin/pinned operations don't reset until GetPinStatusAsync is complete so there is a small delay when the operations update. We can work on trying to optimize this reset in a future PR.

Validation steps performed

PR checklist

• Closes #Environment page should show Unpin from Start Menu / Taskbar once the environment is pinned devhome#2877
• Tests added/passed
• Documentation updated

[sshilov7]

nit: You could catch that exception and use Path.GetTempPath() to account for test scenarious.