Basis of solutions components

[jmhauck]

Copied over from the private solution-creation-app repo:

In the Creation app we added a Configure button on the card when viewing the My Templates page. When you click this button it opens the Configuration modal full screen. This is the first part in in the design for the configuration experience. Note the expectation with these designs is we should use calcite components as much as possible (for example tabs control) rather than sticking specifically to the look in the Balsamiq mockup. We should also use consistent sizing/spacing as we have used in the Solutions app so it feels very familiar.

When you open configuration it should default to the Definition tab and show the Solution Contents tree similar to the item details of the Solution with the first item selected. The Item Details tab allows you to edit the displayed properties of the selected template.

The Data tab for JSON items will display a JSON editor populated with the template's data property. It will also provide variables to simplify the inserting of both organization and solution specific variables.

The Data tab for non JSON items, items who store their data in the resources should provide the ability to download and upload a new version of the resource.

The Properties tab will display a JSON editor populated with the template's properties property.

At the bottom of the Modal should be a Save button (disabled when no changes made) and a Cancel button. All changes should be stored in Memory until you hit Save. If you hit Cancel the changes should be discarded. If you hit the 'X' close button at the top it should ask if you want to Save the changes if there are pending changes.

[jmhauck]

@ajturner the editing of the thumbnail and upload/download for items who store their data in the resources are what I'm going after at the moment.