Move test case recorder into Cursorless engine

[pokey]

Context

As we move to a language server (#946), we need to decide which components will live server side, and which will live in the VSCode extension. The test case recorder presents a challenge, because it references several VSCode apis, but also references many core pieces of our Cursorless engine, such as targets. The test case recorder is also arguably useful beyond Cursorless as a general-purpose VSCode test case recorder, but it is also useful beyond VSCode as a general-purpose Cursorless test case recorder.

Decision

We have decided to have the test case recorder live in the server, rather than in the extension. Whenever we initiate test case recording, VSCode will just send a command to the Cursorless LSP to initiate recording.

Consequences

• The test case recorder can easily capture Cursorless internal state, such as previous that mark, next that mark, hat locations, etc. To capture such state with the recorder living client side would require exposing more internals to the client than we would like
• It will be easier to integrate our test case recorder with other IDEs
• It will be harder to generalise our test case recorder beyond Cursorless test cases
• We need to remove all references to VSCode in the test case recorder
• The test case recorder can easily access information captured by our SpyIDE, which currently is designed to live server side
• The test case recorder can't easily utilise any VSCode-specific apis