Make things build with new module system

[yav]

No testing yet

[chameco]

I've tested the Cryptol module system a bit (with some small changes so SAW will compile given recent changes to the Cryptol branch, see here), and found a minor discrepancy that causes the AWSLC test to fail. Consider the following Cryptol modules:

// test1.cry
module test1 where
parameter
  type foo : #
  bar : [foo]

// test0.cry
module test0 = test1 where
  type foo = 32
  bar = 0xdeadbeef

And the following SAWScript source:

// test.saw
import "test0.cry";
print (eval_int {{ bar }});
print (eval_int {{ `foo : [64] }});

On master, test.saw runs to completion. With the updated Cryptol module system, it prints the value of bar and then produces the following error:

[03:28:55.469] Stack trace:
Cryptol error:
[error] at /tmp/test.saw:4:21--4:24
    Type not in scope: foo

I looked into this a bit, and it looks like foo is no longer present in the Cryptol NamingEnv for the imported module (vs. not being added to some environment on the SAW side).

[RyanGlScott]

Superseded by #1850.