Version management, updates, Dev builds to wasp 🤯

[sktripamer]

Description

1. Version Switching

• wasp version <version> installs/switches to a new Wasp version.
• --force flag enables a hard install from the shell script.
• The most recent release is allowed to sit in the shell wrapper, delegating commands to other wasp binaries depending on the user selection.

2. Updating

• wasp update fetches and installs the latest Wasp version.
• --force flag does a hard install from the shell script.

3. Dev builds

• Massive improvement to the dev experience. ./run install has been overhauled, it fits by default in the new versioning system.
• With the install script, you can run your builds right off the bat on wasp, but protecting your other versions.
• The install script will detect if your build is going to overwrite something, and give you the chance to add a suffix to it (i.e. 0.16.0-dev). Upon successfully building, it automatically puts your new build as the activated wasp version.
• This way, you don't have to worry about your builds, just give them a quick suffix. Great for switching between a massive amount of branches without having to redownload release ones. If you wish, you can overwrite the binary when building
• ./run install --force will hard install your build as the source of truth for the shell wrapper.

Select what type of change this PR introduces:

1. Just code/docs improvement (no functional change).
2. Bug fix (non-breaking change which fixes an issue).
3. New feature (non-breaking change which adds functionality).
4. Breaking change (fix or feature that would cause existing functionality to not work as expected).

Update Waspc ChangeLog and version if needed

If you did a bug fix, new feature, or breaking change, that affects waspc, make sure you satisfy the following:

1. I updated ChangeLog.md with description of the change this PR introduces.
2. I bumped waspc version in waspc.cabal to reflect changes I introduced, with regards to the version of the latest wasp release, if the bump was needed.

Update example apps if needed

If you did code changes and added a new feature or modified an existing feature, make sure you satisfy the following:

1. I updated waspc/examples/todoApp as needed (updated modified feature or added new feature) and manually checked it works correctly.
2. I updated waspc/headless-test/examples/todoApp and its e2e tests as needed (updated modified feature and its tests or added new feature and new tests for it).