Move off of Keytar

[TylerLeonhardt]

With node-keytar now archived and unmaintained, we need a path forward for securely storing secrets and additionally, reflect the fact that we do not need to follow the shape of keytar anymore.

On Desktop, we will take advantage of Electron's safeStorage API. We will also get rid of vscode-encrypt because it would be providing no benefit in this new world.

Additionally, we will remove the KeytarShim that has been in the product. This was the solution to secrets before the SecretStorage API.

Outlined are the steps to get this done:

Tasks

Beta Give feedback

1. Implement new EncryptionService & SecretStorageService services with a migration story. Use new services for extension SecretStorage API
2. Clean up any other direct usecases of old Credentials API and replace them with the new API #186241
   3 of 3
   authentication debt +2
   
3. Write new docs for troubleshooting keyring issues & update remote docs
4. Notify top X extensions of KeytarShim that we will remove it
5. Make discussion post: Keytar Migration Plan vscode-discussions#662
6. Remove keytar shim #115215
   authentication debt +2
   

[TylerLeonhardt]

Closing since everything is done or captured in a follow up issue

[tomduncalf-figma]

Hey @TylerLeonhardt, I just wanted to flag that the behaviour of the secret store onDidChange listener appears to have changed in a surprising way since it was migrated away from keytar: #187247