Add values for types in resources

[bobcatfish]

Added values for the following types, which would be the initial types
we would want to implement and support (could expand to support more in
the future):

• SourceType
• ArtifactType
• ResultTargetType
• PipelineTriggerType and TaskTriggerType
• ParamType (just strings for now?)

Since in #39 @pivotal-nader-ziada and @shashwathi are combining Sources
and Artifacts into one concept, we'll likely combine SourceType and
ArtifactType into one type as well. (Sorry @pivotal-nader-ziada and @shashwathi
this will probably cause some conflicts with your changes but hopefully they'll
be minor to resolve! Lemme know if I can help or if you want me to hold off)

While doing this noticed and cleaned up a couple things:

• Don't need to specify lists of result stores, just one
  for each type (test, log, runs). Also these are identical
  except for their usage, so we can use a common type for all of them
• Turns out pipeline run specs were not defined!
• Updated DEVELOPMENT.md re. how to regenerate generated code
  (such as zz_generated.deepcopy.go)

Fixes #18

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bobcatfish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [bobcatfish]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[nader-ziada]

we will rebase this once its merged and can resolve any conflicts, there are a lot of good clean up here

/lgtm

[nader-ziada]

Maybe we can have a generic interface for result store to make extensible, with runs, logs and tests as implementations of this interface?

[shashwathi]

I like the TaskTriggerRef idea a lot. This is critical information for an operator to know the cause of task run. Great addition.

My Canadian 2 cents: Is ResultTarget a good candidate for interface. Defining the expected behavior rather than restricting it to uploading to a destination. One use case I can think of would be an operator desire to dump logs in DB.

/lgtm
Rest looks great. Awesome work 👍

[tejal29]

LGTM

[bobcatfish]

Is ResultTarget a good candidate for interface. Defining the expected behavior rather than restricting it to uploading to a destination. One use case I can think of would be an operator desire to dump logs in DB.

For sure @shashwathi I think that makes a lot of sense and is definitely relevant to @tejal29 's interests as well :D

My Canadian 2 cents

But we don't even have pennies anymore 😭