CLI install version update

[lukasborawski]

Short Description and Why It's Useful

Update for CLI installation version.

Which Environment This Relates To

Check your case. In case of any doubts please read about Release Cycle

• Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
• RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
• Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

• No upgrade steps required (100% backward compatibility and no breaking changes)
• I've updated the Upgrade notes and Changelog on how to port existing Vue Storefront sites with this new feature
• (Next only) I've followed this instruction and I've created a .js file with information about my Pull Request

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change

Contribution and Currently Important Rules Acceptance

• I read and followed contribution rules

[coveralls]

Pull Request Test Coverage Report for Build 529112922

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.4%) to 93.363%

---

Totals
Change from base Build 520806884:	-0.4%
Covered Lines:	719
Relevant Lines:	766

---

💛 - Coveralls

[github-actions]

💙 vsf-next-demo successfully deployed at https://132c3e5f72730887675458882d83a6058074a335.vsf-next-demo.preview.storefrontcloud.io

[coveralls]

Pull Request Test Coverage Report for Build 530935909

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 93.715%

---

Totals
Change from base Build 520806884:	0.0%
Covered Lines:	1454
Relevant Lines:	1535

---

💛 - Coveralls

[CLAassistant]

All committers have signed the CLA.