Copied tekton pipeline in namespace should reference the source pipeline (and version) in an annotation

The current process for handling pipelines is as follows:

1. Template pipelines and versioned tasks are installed into the template project (`tools` by default). Template pipelines names are not versioned and always use the latest version of the available tasks. All of the tasks are currently project tasks, not cluster tasks...
2. When `oc pipeline` is run, the tasks are copied into the development project (keeping the same name) and the template pipeline is copied into the project although it is renamed to match the repo/app name

A concern was raised about how to maintain and upgrade these pipelines in the development namespace as new versions of the tasks and template pipelines are available. Also, from a traceability perspective it would be good to understand where the pipeline in the project came from.

To that end, we should make a couple of updates to the pipeline definition:

1. Include source control annotations in pipeline, e.g.

```yaml
app.openshift.io/vcs-ref: master
app.openshift.io/vcs-uri: https://github.com/IBM/ibm-garage-tekton-tasks
```

2. Include the version label like we do in the tasks, e.g.

```yaml
labels:
version: 2.3.0
```