fix: resolve LS exported types error

Description

When running latest (unreleased) version of LS inside vscode, the build fails with errors related to missing AIContextItem types.

This is another occurence of the same issue we have seen a bunch of times - the types inside LS workspace packages are not correctly bundled and exported with the LS assets, which means the vscode build fails due to these types being missing.

This MR hacks around the problem like usual by duplicating type information from LS into vscode, in order to unblock LS releases. The proper fix is tracked by gitlab-org/editor-extensions&190

Related Issues

Resolves #2142 (closed)

How has this been tested?

Build passes ✅

No functional changes expected.

(Note the failure can be reproduced by linking LS main into vscode main)

• If src/browser or src/common has been modified, please consider interoperability with the Web IDE. See Running the Extension in WebIDE.
• Consider an end-to-end test for significant new features that aren't covered by integration tests.

Screenshots (if appropriate)

What CHANGELOG entry will this MR create?

• fix: Bug fix fixes - a user-facing issue in production - included in changelog
• feature: New feature - a user-facing change which adds functionality - included in changelog
• BREAKING CHANGE: (fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog
• None - other non-user-facing changes

Closes #2142 (closed)