Support for custom app versioning (non-semantic)

[RunsFor]

Right now, cartridge-cli requires cartridge apps to have semantic versioning even for tar.gz packages. However, customers may have their own version policies for their apps. Can we add support for custom version policies?

Here is a reproducer:

$ cartridge create --name myapp
   • Create application myapp
   • Generate application files
   • Initialize application git repository
   • Application "myapp" created successfully
$ cd myapp
$ touch file
$ git add file
$ git commit -m "update repo"
[master 091637d] update repo
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 file
$ git tag v0.1.0
$ cartridge pack tgz .
   • Packing myapp into tgz
   ⨯ Version should be semantic (major.minor.patch[-count][-commit])

[Totktonada]

I would propose to solve #415 and suggest to pass VERSION variable if tags are different from X.Y.Z schema (say, have 'v' prefix).

[Totktonada]

However, okay, those are different issues. Your (and #552) proposal is about arbitrary versioning.

[Totktonada]

To be honest, I don't know why the decision about enforcing semver was made. So I don't know, whether it'll be appropriate to change it.

@dokshina Can you shed some light there?

[Kasen]

I know that history. This decision was made by @knazarov cause forcing of right practice is a good thing.