Vsc build updates

[yurm04]

WHY are these changes introduced?

• The entire monorepo was getting packaged up with the extension on vsce package
• Get ready for v0.2.0
• Bring up to speed with main

WHAT is this pull request doing?

• updating the .vscodeignore to exclude everything outside of polaris-for-vscode and .turbo
• bump the version to v0.2.0
• merge main

[changeset-bot]

⚠️ No Changeset found

Latest commit: cf78bf2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[yurm04]

for some reason the vsce cli will package up the entire repo with the extension without this. I'm hoping this won't be necessary after @romellogoodman's PR to add rollup as a build tool #5802

[aaronccasanova]

Might be helpful to include a comment here since it's resolving a specific edge case. I don't know the ignore pattern off the top, but we could also try to make this self documenting with a negated pattern e.g. ignore everything that's not polaris-for-vscode

../**
!../polaris-for-vscode

[sam-b-rose]

I did some digging here and seems like there still ins't official support for vsce package for yarn workspaces

This should be a problem if we are bundling node_modules with the package using webpack or rollup (I think) according to this comment