Add 0.17 manifests into the operator

[houshengbo]

Fixes: #253

Proposed Changes

• This PR added the 0.17 manifests into the operator.
• The Upgrade Prow changed the previous version of Knative into 0.16.

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: houshengbo

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 [houshengbo]

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

[evankanderson]

Is there a script that picks these up and redoes the naming, or is that by hand?

[evankanderson]

(The question about the script was for the kodata files, the test file change clearly needs some human TLC.)

[evankanderson]

I wonder if it's worth setting up a script to sync the releases files into these directories, and then have automation do the copy.

Right now, I'm looking that the files exist, but I'm not (for example) checking that they have exactly the same bytes as the ones released by the upstreams.

[houshengbo]

/test pull-knative-operator-upgrade-tests

[houshengbo]

@evankanderson So far, this is done manually.

[houshengbo]

/test pull-knative-operator-upgrade-tests

[houshengbo]

/retest

[houshengbo]

/test pull-knative-operator-upgrade-tests

[evankanderson]

/lgtm

I can take a shot at writing a script to generate these.

I noticed that you've added a numeric prefix to the manifests; any rules you've got about how to number the files?

[houshengbo]

All resources:
CRDs first, post jobs last.

For other resources in the middle:
Key component first(core files), other components second.

[houshengbo]

/test pull-knative-operator-integration-tests

[houshengbo]

/test pull-knative-operator-upgrade-tests

[Cynocracy]

/lgtm