Update a couple transcripts to the new formatting

These aren‘t run as part of ./scripts/check.sh, so they got missed in the initial pass.

unison-src/builtin-tests/interpreter-tests.output.md

@@ -4,7 +4,7 @@ If you want to add or update tests, you can create a branch of that project, and
 
 Before merging the PR on Github, we'll merge your branch on Share and restore `runtime_tests_version` to /main or maybe a release.
 
-```ucm
+``` ucm
 runtime-tests/selected> run tests
 
   ()

unison-src/builtin-tests/jit-tests.output.md

@@ -4,7 +4,7 @@ If you want to add or update tests, you can create a branch of that project, and
 
 Before merging the PR on Github, we'll merge your branch on Share and restore `runtime_tests_version` to /main or maybe a release.
 
-```ucm
+``` ucm
 runtime-tests/selected> run.native tests
 
   ()
@@ -17,7 +17,8 @@ runtime-tests/selected> run.native tests.jit.only
 Per Dan:
 It's testing a flaw in how we were sending code from a scratch file to the native runtime, when that happened multiple times.
 Related to the verifiable refs and recursive functions.
-```unison
+
+``` unison
 foo = do
   go : Nat ->{Exception} ()
   go = cases
@@ -26,20 +27,20 @@ foo = do
   go 1000
 ```
 
-```ucm
+``` ucm
 
   Loading changes detected in scratch.u.
 
   I found and typechecked these definitions in scratch.u. If you
   do an `add` or `update`, here's how your codebase would
   change:
-  
+
     ⍟ These new definitions are ok to `add`:
-    
+
       foo : '{Exception} ()
 
 ```
-```ucm
+``` ucm
 scratch/main> run.native foo
 
   ()
@@ -53,14 +54,14 @@ This can also only be tested by separately running this test, because
 it is exercising the protocol that ucm uses to talk to the jit during
 an exception.
 
-```ucm
+``` ucm
 runtime-tests/selected> run.native testBug
 
   💔💥
-  
+
   I've encountered a call to builtin.bug with the following
   value:
-  
+
     "testing"
 
 ```