fix: pin error focuses the view instead of the view container

[tysoncung]

Problem

When clicking "Pin Error" in the tooltip, the command reveals the view container using workbench.view.extension.prettyTsErrors. If the user has moved the Pretty TS Errors webview view to a different view container (e.g. the Explorer sidebar), this command focuses the original (now potentially empty) container instead of where the view actually lives — causing an unexpected view switch.

Fix

Changed to use prettyTsErrors.sidePanel.focus which focuses the specific webview view regardless of which container it has been moved to. VS Code automatically generates a .focus command for each registered webview view.

Testing

1. Move the "Pretty Typescript Errors" view to a separate view container (drag it to the Explorer sidebar or secondary sidebar)
2. Focus the Pretty TS Errors view
3. Hover over a TypeScript error and click "Pin Error"
4. The Pretty TS Errors view should remain visible — previously it would switch to the Explorer view

Fixes #182

[kevinramharak]

@tysoncung Thanks that was quick.

@yoavbls https://github.com/yoavbls/pretty-ts-errors/pull/181/changes explicitly set it to workbench.view.extension.prettyTsErrors maybe a mistake after renaming the panel from markdownPreview to sidePanel?

[yoavbls]

Yes, it's probably my mistake after renaming the panel.
Thank you 😊