`wheels new generates` only creates application only with Wheels 3.x application instead of both Wheels 4.0 (Bleeding Edge)

[zainforbjs]

Describe the bug
Running the new Wheels CLI command wheels new myApp creates an application based on Wheels version Wheels 3.1.x, but not with the new version Wheels 4.x.
This was being handled by the argument/parameter named template that provides the option of both stable main branch code and also the develop (bleeding edge) code.
There appears to be no option in the current 4.0 CLI to explicitly generate a bleeding-edge / snapshot Wheels 4 application, unlike the older CLI behavior.

Previous behavior (Wheels 3 CLI)
Previously, it was possible to generate a bleeding-edge application using:

wheels g app --template=wheels-base-template@BE

This allowed developers to scaffold the latest development version of Wheels.

Current behavior
Using:

wheels new myApp

creates an application using Wheels 3.x conventions/templates by default.

There also does not appear to be a documented or available option to generate a Wheels 4 bleeding-edge application.

To Reproduce

1. Install the latest LuCLI-based Wheels CLI
2. Run:

wheels new myApp

3. Start the server using

wheels start

4. hit the wheels developer info page /wheels/info/.
5. Observe that:

• generated structure/configuration matches Wheels 3.x
• not Wheels 4.0

Expected behavior

• One of the following should happen:
  wheels new should generate a Wheels 4 application by default
  OR
• The CLI should provide a documented option to generate:
  • Wheels 4 stable
  • Wheels 4 bleeding-edge/snapshot applications

Example:

wheels new myApp --snapshot

or equivalent.

Actual behavior

• wheels new generates a Wheels 3.x application
• No obvious/documented way to generate a Wheels 4 bleeding-edge application

Desktop:

• OS: Any