Add saw-remote-api tests to CI

[pnwamk]

to avoid bitrot and the like.

To that end, we recently we missed an update to a SAW record (I'll make a PR for it soon(TM)):

commit d4a6f8b5a855c647563dce25c7ab82787f90555f (master)
Author: Andrew Kent <andrew@galois.com>
Date:   Tue Dec 8 12:46:16 2020 -0800

    Fix missing record field error in SAWServer.

diff --git a/saw-remote-api/src/SAWServer.hs b/saw-remote-api/src/SAWServer.hs
index f6c98ecf..7bb622dc 100644
--- a/saw-remote-api/src/SAWServer.hs
+++ b/saw-remote-api/src/SAWServer.hs
@@ -187,6 +187,7 @@ initialState readFile =
 #else
                 , roProxy = AIGProxy AIG.basicProxy
 #endif
+                , roBasicSS = ss
                 }
          rw = TopLevelRW
                 { rwValues = mempty

[atomb]

For some additional context, the tests currently do run in CI, but they're allowed to fail since there's a bunch more work we need to do to set up the environment for them to work correctly.

[pnwamk]

Fixed - servers are now tested in CI. See #1118