Add `test-with` field to `juvix.yaml` for Juvix compiler version specification

[jonaprieto]

Introduce a new field named test-with (or an alternative name, feel free to suggest another) in the juvix.yaml configuration file. This addition allows users to specify the necessary Juvix version for compilation and typechecking, with the expectation of testing the codebase at minimum. This improvement streamlines the process of testing the codebase using different Juvix versions and helps identify potential breaking changes in the compiler.

Expected shape of the juvix.yaml file:

name: Your project name here
test-with: 0.3.3

[vrom911]

Would this be for the "documenting" purposes only (like it is in Haskell, for example), or it is expected more from this field?

Also, it seems that it would make sense for this field to be the list of all compatible compiler versions.

Though, it is not clear how to verify it as we do not have the list of all released compiler versions as well.

[jonaprieto]

Would this be for the "documenting" purposes only (like it is in Haskell, for example), or it is expected more from this field?

This is not only for documentation purposes. I'd like the compiler to independently attempt to type check/compile a project and notify the user to upgrade the version in the configuration file if it is lower (maybe after a successful run?). Or alternatively, it should warn the user to upgrade Juvix if the version is higher in the configuration file than the one installed.

Also, it seems that it would make sense for this field to be the list of all compatible compiler versions.

Perhaps, not sure. To make our life easier, one version seems to be good enough and simple. Also, I don't think people would test the packages with different Juvix versions, the language is not stable yet, so they should hang on to the latest Juvix version.