Spike storefront installation on CI and QA

[plabadie]

We don't ship a shell app anymore. Customers are provided setup instructions to create a brand new angular app and add the libs to it. We should use this scenario to install our storefront on the pipeline to continuously catch code updates that would have a side effect on the end result.

Another requirement: Use the same installation script for QA environments and the CI.

[Xymmer]

I imported the 3 jira tickets created by Patrick earlier: #172, #173, #174.

[Xymmer]

we'll use this ticket as a spike for what to do next

[plabadie]

After investigation, here is what we could do:

ALIGN QA WITH SETUP INSTRUCTIONS

• Align the QA installation script with the installation steps we promote/document. https://github.com/SAP/cloud-commerce-spartacus-storefront/blob/develop/docs/setupandinstallation.md

• We should improve the team awareness that the setup instructions and the QA installation steps are related and both need updating in the dod of some tickets that would have an impact on them, since the CI does not perform this type of installation checks yet.

• Let's perhaps run the updated script in QA for a while before propagating it to the CI.

INSTALLATION STEP VALIDATION ON CI

• Implement an 'installation check' on the pipeline -- that shares the core logic with with the QA installation script. -- that installs and builds the app and checks for defects, like build errors, dependency warnings (but no runtime validation like e2e yet)

[plabadie]

A draft implementation was produced and works if we wish to explore this scenario further. https://stash.hybris.com/projects/C3PO/repos/spartacus-installation/pull-requests/14/diff.

With a few tweaks, this would address the "Align QA with setup instructions" feature described int the previous comment.