Move generated CRDs to the OCP versioned target manifest folder

[periklis]

Motivation

Besides the elasticsearch-operator project using the operator-sdk to generate code and CRDs it doesn't clearly adhere to the operator-sdk project structure. Thus, this PR extends the Makefile to move generated CRDs to the target manifest folder.

Depends on #277

[periklis]

/hold need for rebase after dependencies are meged.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: periklis
To complete the pull request process, please assign jcantrill
You can assign the PR to them by writing /assign @jcantrill in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[jcantrill]

@alanconway Doesn't your equivalent to CLO remove operator-sdk generated manifests? I think this PR is in the wrong direction

[periklis]

@jcantrill The PR applies the same as https://github.com/openshift/cluster-logging-operator/pull/413/files#diff-b67911656ef5d18c4ae36cb6741b7965R76

[periklis]

/hold

[openshift-ci-robot]

@periklis: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-operator	07ffdf1	link	/test e2e-operator
ci/prow/cluster-logging-operator-e2e	07ffdf1	link	/test cluster-logging-operator-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[periklis]

We concluded in our arch meeting to not use this approach. Thus I close this PR.