Lazy Initialization of IR Types causes a bug in Type::fromKind

[emmanuel099]

Describe the bug

Type inference has a problem when the type has not be used in the specification, but the type kind is used for the inference.

To Reproduce

Executing the following example gives an unable to infer type, @4{1eee} error for undef. But this example should be resolvable, because we expect a bool and thus the inference can use this fact to resolve the type of undef.

CASM init foo

rule foo =
    if undef then
        skip

Expected behavior

Type the undef as boolean and give an error during execution.

Additional context

The IR Type::fromKind returns an empty list because the lazy initialization is not performed.