Fix @vscode/chat-lib install script and package

[jeffreyhunter77]

This fixes a few problems with the @vscode/chat-lib package after the addition of inline completions:

• script/postinstall.ts was omitted from the package
• The install script didn't handle the different ways npm might install the @vscode/tree-sitter-wasm package
• applicationinsights must be listed as a standard dependency, not a dev dependency

[Copilot]

Pull request overview

This PR fixes issues with the @vscode/chat-lib package's installation process after inline completions were added. The changes ensure the package can be properly installed and configured in different npm environments.

Key Changes:

• Modified postinstall script to dynamically resolve the @vscode/tree-sitter-wasm package location instead of assuming a fixed path
• Moved applicationinsights from devDependencies to dependencies to ensure it's available at runtime
• Added the script directory to the package files list so the postinstall script is included in published packages

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
chat-lib/script/postinstall.ts	Added treeSitterWasmDir() function to dynamically resolve tree-sitter-wasm location and updated asset copying to use resolved paths
chat-lib/package.json	Moved applicationinsights to dependencies, added script directory to package files

Files not reviewed (1)

• chat-lib/package-lock.json: Language not supported

[Copilot]

The function assumes WASM files are in the same directory as the resolved module entry point, but require.resolve() resolves to the package's main entry file (typically index.js). The WASM files are in a wasm/ subdirectory. The path should be path.join(modulePath, 'wasm') to correctly locate the WASM files.

Suggested change

	return path.relative(REPO_ROOT, modulePath);
	return path.relative(REPO_ROOT, path.join(modulePath, 'wasm'));