Fix composer develop install issues

[mvorisek]

fixes #193

these two lines should stay on release (they are for root composer project only, they may still be required for dev deps):

  "minimum-stability": "dev",
  "prefer-stable": true,

but this one:

  "version": "dev-develop",

should be remove completely on release.

For all repos.

[DarkSide666]

• in current develop branch composer updates fine
• in develop branch with version:dev-develop composer updates fine
• in another branch without version:dev-develop composer DO NOT UPDATE - atk4/data dev-develop requires atk4/core dev-develop
• in another branch with version:dev-develop composer updates fine

So it looks that adding version:dev-develop solves this issue.

[DarkSide666]

If we can replace, then something like this should work already:

// these will be used in develop
"version": "dev-develop",
"minimum-stability": "dev",
"prefer-stable": true,

// these will be used when releasing
"version-release": "something",
"minimum-stability-release": "something",
"prefer-stable-release": true,

[DarkSide666]

TODO - need to add another jq line in core/.github/workflows/bundler.yml to completely remove version key from json while releasing.

[mvorisek]

composer config version --unset seems to be much cleaner approach

I think we can also remove require(-dev)?-release completely and in release process replace all (?<=atk4/xxx: )dev-* requires with ^version

here is how to get a version: https://github.com/atk4/ui/blob/09ae0f67deda221ba2f48d6d3beb00be01e7a010/.github/workflows/bundler.yml#L41

[mvorisek]

@romaninsh @DarkSide666 updated post about deps, wdyt? Very robust if we can let the release script do the work...

[DarkSide666]

having ...-release is still ok for now, so let's not complicate this at this point.