feat: Add builds next option

[neznaika0]

Description

• A small improvement to upgrade to the dev branch: 4.7 | dev-develop | 4.8-dev

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[michalsn]

I'm not a big fan of introducing next, as it will require an update that we will most likely forget to make.

Additionally, removing the instructions on how to adjust the composer file manually will leave people clueless about what to do.

I would agree to introducing something like allowing a version number to be specified, for example: 4.8, 4.9, etc., which would result in a proper, explicit change - but this parameter would need to come with a detailed explanation.

[neznaika0]

We have a workflow for the appstarter release. What if I replace the constant for task?

Honestly, I do not know if anyone uses the dev version except me.

If we continue, it is advisable to specify the next CI version with the release. Because the dev has the current number 4.7.0. In fact, it's 4.7.1 or 4.8.0. module-manager won't forgive this.

[michalsn]

We have a workflow for the appstarter release. What if I replace the constant for task?

If the version can be adjusted automatically for the next minor release, then I would accept this.

Honestly, I do not know if anyone uses the dev version except me.

Yes, it's used.

If we continue, it is advisable to specify the next CI version with the release. Because the dev has the current number 4.7.0. In fact, it's 4.7.1 or 4.8.0.

Not sure about it. As it could lead to a situation where someone thinks they are using version ie, 4.8, which is not the "real" version 4.8.

[neznaika0]

I understand, that's why I indicated the note in the manual.
I manually changed the version in vendor/ to work.

[neznaika0]

0. Paste here?
   https://github.com/codeigniter4/CodeIgniter4/blob/develop/admin/prepare-release.php

1. We are creating a new 4.8.0.rst if it is automatic? take the logic of the minor version from there.

2. Another way is to add to the description of the release steps

[michalsn]

Looks good.

[michalsn]

Thank you @neznaika0