MXNet Operator: Consolidate manifests

[yanniszark]

Umbrella-Issue: kubeflow/manifests#1769

MXNet Operator

Current manifests structure

.
├── base
├── mxnet-operator
│   ├── base
│   └── overlays
│       └── application
└── overlays
    ├── v1
    └── v1beta1

Explanation

• mxnet-operator came from kubeflow/manifests
• base and overlays already existed in the repo
• The application overlays contain Application CRs, which we want to move away from (Why do we need kubernetes-sigs/application controller in Kubeflow? manifests#1715 (comment))

We'll add a kubeflow overlay to the existing overlays folder, which will import overlays/v1, as that's the version of upstream manifests.

Recommended end state

.
├── base
└── overlays
    ├── kubeflow
    ├── v1
    └── v1beta1

[yanniszark]

cc @kubeflow/wg-training-leads

[yanniszark]

/retest

[gaocegege]

/lgtm

/assign @kubeflow/wg-training-leads

[terrytangyuan]

/approve

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: terrytangyuan, yanniszark

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

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