Revert "[fcos] add a new upstream community operator source"

[vrutkovs]

Reverts #3487

OperatorHub.io has two community operator collections - "upstream-community-operators" and "community-operators". Submissions start at "upstream-community-operators" and if its known to work with OCP/OKD it would be cloned in "community-operators". As a result, its pointless to add a source which has known to be faulty operators in OKD out of the box.

Related to okd-project/okd#99

@dmesser correct me if description is not correct.
/cc @LorbusChris

[LorbusChris]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

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

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-vsphere	0efe737	link	/test e2e-vsphere

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.

Details

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.

[vrutkovs]

Oh, I didn't cherry-pick this commit in the branch we force pushed. So its effectively reverted now :)