Use term `release` instead of `version` for LionWeb?

[enikao]

I'd like to disambiguate version (as in version control) and release (as in labeled, stable state of LionWeb).

We currently use the term version at:

Serialization:

1. SerializationChunk, field serializationFormatVersion
2. UsedLanguage, field version
3. MetaPointer, field version

Metamodel:

1. Language, field version

Of the above, I'd change serializationFormatVersion to serializationFormatRelease.

The other occasions refer to the user-controlled language version. I'm not sure whether we want to change them.

[dslmeinte]

I like serializationFormatRelease because we're likely to have very few versions of that, and each of these probably doesn't need to go through a development/pre-lease lifecycle that benefits from being explicit in the version ID.

For the other things, it's much more likely there's a development/pre-lease lifecycle that benefits from being explicit, so I'd be hesitant to flip that over to <xxx>Release just yet.

[enikao]

On 2023-09-29, we decided NOT to use term "release".

Rationale:

• We have many kinds of “version” anyway
• We don’t oversee all implications
• serializationFormatVersion is specific enough

[enikao]

Note: in #58, we decided to keep serialization format version and M3 version in lockstep.