Clarify use case of operator-sdk run bundle(-upgrade) in documentation

[everettraven]

Recently, in various communication channels, there have been questions around using the operator-sdk run bundle(-upgrade) command for non-testing purposes. I think this has to do with some pretty strong suggestions in our documentation that operator-sdk run bundle(-upgrade) is useful for deploying operators with OLM but lacking the caveat that this if for local dev / testing purposes only and should not be used for deploying operators in production. We do call this out in https://sdk.operatorframework.io/docs/olm-integration/testing-deployment/#caveats but I have a feeling this is being overlooked and should revise our docs to better reflect this caveat everywhere operator-sdk run bundle(-upgrade) is referenced / suggested.

[michaelryanpeter]

/assign

[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