feat: allow formatting and linting of in-memory files

[nhedger]

This PR loosens the constraints of the document filter to allow linting and formatting in-memory files.

Related to biomejs/biome#1413

---

Fixes #35

[jsejcksn]

@nhedger

Will this change allow the extension to format a document in the scenario described in the linked issue?

Ref:

• 🐛 Format the content of an in-memory editor in VS Code without configuration biome#1394

1. Close all VS Code windows and quit the app. Open a fresh instance of VS Code with a blank window and no workspace.
2. Open a new editor tab and paste in some copied source code text (e.g. TypeScript)
3. Verify that the language mode of the editor is correct for the pasted content (e.g. TypeScript) — in the case that it wasn't correctly auto-detected
4. Use the VS Code command "Format Document" from the command palette

…whether or not there are any filesystem artifacts (like a config file), etc.

/cc @ematipico

[nhedger]

Assuming that the extension is configured not to require the config file to be present, I believe it would work, but I'd have to try it to be certain.

I'll take a look tomorrow

[jsejcksn]

@nhedger

Assuming that the extension is configured not to require the config file to be present

Is this something that the user needs to explicitly configure? If so, what steps are needed?

I'll take a look tomorrow

Thanks — looking forward to it!

[nhedger]

Is this something that the user needs to explicitly configure? If so, what steps are needed?

The biome.requireConfiguration option must be set to false. Currently true is the default.

In a future version of the extension this setting will be removed, so no user interaction will be needed.