Provide end user as well as support persona the ability to identify in a Git repo, the source for a starter-created project.

[scottkurz]

With a typical flow creating from a starter, after doing:
$ odo create java-openliberty --starter
you should have a devfile referencing, as its parent, a specific version of the java-openliberty application stack devfile.

However, the starter artifacts will not necessarily be versioned along with the stack devfile and Docker image. The starter could be updated and another project could be created from the same stack version, but with a different starter.

This shouldn't be a big deal, since a user will be customizing the starter themselves.

Every time the stack is updated, it should be tested to ensure a project created from the latest version of EACH starter will worth with this most recent stack version. It won't effect existing projects which should be pinned to an existing version of the devfile.

Every time a starter is update it should be tested to ensure it works with the latest version of the stack.

ASSUMPTION: Once a project is created, it does not use starters again, so it isn't possible for a change in starter to break an existing project. Note, this assumes something like an "application project". You could say here's my "test project", which always does a create from starter, so yes, it is effected by a change in starter at a given stack

At the very least, we should include, within the starter project (POM?) a reference to the SHA that shows the original starter source cloned from the Git repo hosting it.

[scottkurz]

This issue should probably be left alone until the support for having odo create reference parent devfiles, and for versioning those parent devfiles, is clarified.

[scottkurz]

Subsumed under #60, closing as dup