Show error message if backing up credential file fails

[dotNomad]

This PR adds a new AgentError that bubbles up if operations in the backing-up of the credential file fail, showing the user the message so they may take action on it.

Intent

Resolves #2513

Type of Change

• • Bug Fix
• • New Feature
• • Breaking Change
• • Documentation
• • Refactor
• • Tooling

User Impact

Now a notification will be shown with the specific error that occurred when backing up a credential file, with an error code that we can do more with in the future.

Automated Tests

Automated tests were added to ensure that the correct data is sent back when the reset API errors.

Directions for Reviewers

Ensure that the error bubbles up via the API, is shown as a notification, and works in Workbench.

[sagerb]

I verified this functionality on the mac, by doing the following. It is easier to make these modifications to the codebase temporarily than debug the change on workbench. I'm confident that the functionality is the same.

1. I modified the code to eliminating keyring support, and started VSCode with the extension
2. I created a valid credential using the UX, so I had a valid .connect-credentials file and exited VSCode.
3. I replaced it with a file with ZZZ in it (using echo "zza" > .connect-credentials)
4. I then made it write-only with the command chmod -r .connect-credentials.

On launching and activating the extension, I then saw the new error message, with the low-level details of the OS call, which is what we wanted:

I do feel that we need to update the messaging on this error, as we're not communicating the context to the user that their credentials are corrupt (and we can't do anything about it).

[dotNomad]

I do feel that we need to update the messaging on this error, as we're not communicating the context to the user that their credentials are corrupt (and we can't do anything about it).

Fantastic point. Let me get that messaging tweaked, and I'll request a re-review.

[sagerb]

Existing code looks great, but as mentioned in my verification note, we should update the error message to indicate that the user's credentials are corrupt and provide some action path for them to resolve.

Currently:

Failed to backup credentials to /Users/billsager/.connect-credentials-2025-01-09: open /Users/billsager/.connect-credentials: permission denied

Perhaps:

Corrupted credentials data found. Failed to resolve this issue by backing up credentials to /Users/billsager/.connect-credentials-2025-01-09: open /Users/billsager/.connect-credentials: permission denied" prior to resetting.

(Just a start ^^^)

[dotNomad]

Existing code looks great, but as mentioned in my verification note, we should update the error message to indicate that the user's credentials are corrupt and provide some action path for them to resolve.

Pushed up a change. Now the error will read:

Unrecognizable credentials for Posit Publisher were found. Failed to backup credentials to /Users/billsager/.connect-credentials-2025-01-09: open /Users/billsager/.connect-credentials: permission denied

[sagerb]

LGTM