Need to support multiple versions

[bthaile]

Currently flix only has one version (1.0.0)
Soon there will be version 1.1.0, need an approach to managing multiple versions. Some thoughts:

1. (strict) Force flix to be migrated to newest version before they can be executed or bindings generated
2. (lax) Have version specific logic for executing and generating bindings files (might not be much specific logic needed from version to version)
3. (mixed) Allow executing all versions and only support generating binding files on current version. Then users would only have to migrate flix to generate binding files.
4. (kick can) Decide later and only support current version at development time.

[JeffreyDoyle]

What we did in FCL is migrate the interaction template up to the latest possible version (https://github.com/onflow/fcl-js/pull/1614/files#diff-4843d2991b66a45e6a6fb0f2932805766a150102c668b23b514407433e5e72ea) prior to it's use.