UPSTREAM: <carry>: Switch tools management to bingo

[rashmigottipati]

All the files in .bingo are auto-generated

Upstream PR: operator-framework/ansible-operator-plugins#59

[rashmigottipati]

cc @everettraven @oceanc80 @grokspawn

[everettraven]

The change itself looks good to me, but we shouldn't use a carry commit here. This should essentially be a rebase on top of the upstream changes similar to how it is done for the OLMv1 repos - example of catalogd: openshift/operator-framework-catalogd#38

https://docs.google.com/document/d/1DrLUbo0CByTDv9Jxc5RJCqZgG5Ivlc-BCh_qASQooq0/edit#heading=h.cwvtj4ajzja1 Should have more explicit instructions on how to do this. Some of the info about having a spreadsheet I don't think is necessary but this process should in general be pretty accurate as to what needs to be done.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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-sigs/prow repository.