WIP: linter host, VFS, and other related experiments

[auvred]

PR Checklist

• Addresses an existing open issue: fixes #000
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

This PR fixes the following issues:

• Fixes 🚀 Feature: introduce Vue language #1113
• Fixes 🐛 Bug: virtual FS in TS based language incorrectly defaults to ScriptKind.TS for non-TS languages #1142
• Fixes 🚀 Feature: allow configuring virtual fixture files in RuleTester #621
• Fixes 🚀 Feature: Unify disk (project service) and virtual (vfs environments) TypeScript files #73

All these issues depend each on other and it's easier to experiment on a new architecture while testing that it moves all these issues in the right direction.

(Edited by @lishaduck to link the fixes so GH'll pick them up)

[vercel]

@auvred is attempting to deploy a commit to the SquiggleTools Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Hi @auvred, thanks for the pull request! A scan flagged some concerns with it. Could you please take a look?

[pr-title-conventional] The PR title has an unknown type: 'WIP'. Known types are: 'build', 'chore', 'ci', 'docs', 'feat', 'fix', 'perf', 'refactor', 'revert', 'style', 'test' This repository asks that pull request titles start with a type in the Conventional Commits format. Doing so helps make the purpose of each pull request clear for humans and machines. To resolve this report, replace the current type with one of those known types, like "feat: linter host, VFS, and other related experiments".

[pr-task-completion] This PR's body is missing [x] checks on the following tasks from the PR template.

• Addresses an existing open issue: fixes #000
• That issue was marked as status: accepting prs

Repositories often provide a set of tasks that pull request authors are expected to complete. Those tasks should be marked as completed with a [x] in the pull request description. Please complete those tasks and mark the checks as [x] completed.

🗺️ This message was posted automatically by OctoGuide: a bot for GitHub repository best practices.

[lishaduck]

This probably isn't an issue with this PR, but when I think "TypeScript language plugin" I think compilerOptions.plugins. "Volar plugin for Svelte"?
I guess long term, we'll want to extract style blocks & HTML out as well?

[lishaduck]

Oh, wait I think it's just a copy-paste error.

Suggested change

	"description": "[Experimental] TypeScript language plugin for Flint.",
	"description": "[Experimental] Svelte language plugin for Flint.",

[auvred]

Oh, yeah! Thanks for pointing that out. I'm planning to reconcile the package.json/tsconfig.json/etc. setups once I'm closer to finishing my experiments, so the new package setup aligns with your ongoing effort to overhaul our tooling.

[auvred]

Closing in favor of #2315