raw/metadata.json: add historical metadata from quay

[steveej]

The metadata in this has been manually added on quay in the past. It's
my understanding that we don't plan to a convenient mapping for adding
edges using previous.add, so we don't want a convenience structure for
this.

---

This is part of openshift/cincinnati#226.

[wking]

For context, we need these post-release edge injections to preserve this portion of the prerelease-4.1 Cincinnati graph:

because those edges are not included in the release image metadata (which is our current best-practice):

$ for TAG in 4.1.0-rc.6 4.1.0-rc.7 4.1.0-rc.9 4.1.0; do echo -ne "${TAG}\t"; oc adm release info "quay.io/openshift-release-dev/ocp-release:${TAG}" | grep Upgrades; done
4.1.0-rc.6	  Upgrades: <none>
4.1.0-rc.7	  Upgrades: <none>
4.1.0-rc.9	  Upgrades: <none>
4.1.0	  Upgrades: <none>

/lgtm

(but will need a release admin to approve).

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: steveeJ, wking

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [steveeJ,wking]

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

[wking]

...(but will need a release admin to approve).

or not, because @steveej was authorized to approve the change being made by the initial PR? Or because he's allowed to create new directories that get delegated to other approvers? Or something like that.