Specify the development lifecycle step of a command

[l0rd]

We need to agree on a convention to specify the step(s) of the development lifecycle a command belongs to. For example a given command will be used during the build step and another one is used for the run step. Tools like odo and che will then leverage this information to infer the sequence of the commands that need to be run.

A possible convention we can agree on is to specify the lifecycleStep as command annotation:

commands:
  - exec:
      annotations:
        lifecycleStep: build
      commandLine: "./build.sh"
      component: build-container
  - exec:
      annotations:
        lifecycleStep: run
      commandLine: "./run.sh"
      component: runtime-container

[davidfestal]

Is it a duplicate of #27 ?

Additionally, about the syntax proposed here: do we assume annotations would be some sort of free map (without a sub-schema) ?
Why not add this as a real field in the command schema itself ?

[l0rd]

Closing as duplicate of #27