Move typescript tests to new runner (#3696)

# Description of Changes

<!-- Please describe your change, mention any related tickets, and so on
here. -->

- This just moves the typescript tests onto the custom runner.

|Test|Before|After|% Change|
|---|---|---|---|
|Typescript - Lint|1m|<1m|No change|
|Typescript - Build + Test|14m|5m|64%|

# API and ABI breaking changes

None

<!-- If this is an API or ABI breaking change, please apply the
corresponding GitHub label. -->

# Expected complexity level and risk

1 - if the typescript tests become flaky this could be the reason.

<!--
How complicated do you think these changes are? Grade on a scale from 1
to 5,
where 1 is a trivial change, and 5 is a deep-reaching and complex
change.

This complexity rating applies not only to the complexity apparent in
the diff,
but also to its interactions with existing and future code.

If you answered more than a 2, explain what is complex about the PR,
and what other components it interacts with in potentially concerning
ways. -->

# Testing

- [x] The typescript CI still passes and is faster.

<!-- Describe any testing you've done, and any testing you'd like your
reviewers to do,
so that you're confident that all the changes work as expected! -->

---------

Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>

Author: jdetter

.github/workflows/typescript-lint.yml

@@ -9,7 +9,11 @@ on:
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: spacetimedb-new-runner
+    container:
+      image: localhost:5000/spacetimedb-ci:latest
+      options: --privileged
+
 
     steps:
       - name: Checkout repository

.github/workflows/typescript-test.yml

@@ -13,7 +13,10 @@ concurrency:
 
 jobs:
   build-and-test:
-    runs-on: ubuntu-latest
+    runs-on: spacetimedb-new-runner
+    container:
+      image: localhost:5000/spacetimedb-ci:latest
+      options: --privileged
     env:
       CARGO_TARGET_DIR: ${{ github.workspace }}/target
 
@@ -93,8 +96,8 @@ jobs:
           cargo install --force --path crates/cli --locked --message-format=short
           cargo install --force --path crates/standalone --locked --message-format=short
           # Add a handy alias using the old binary name, so that we don't have to rewrite all scripts (incl. in submodules).
-          rm -f $HOME/.cargo/bin/spacetime
-          ln -s $HOME/.cargo/bin/spacetimedb-cli $HOME/.cargo/bin/spacetime
+          rm -f $CARGO_HOME/bin/spacetime
+          ln -s $CARGO_HOME/bin/spacetimedb-cli $CARGO_HOME/bin/spacetime
           # Clear any existing information
           spacetime server clear -y