As an operator author, I don't want to have to think separately about `olm.bundle.object` properties while using `opm render` to include a bundle in my plain-text catalog metadata file. 

Currently, following the steps here to build a catalog is insufficient for users expecting integration with packageserver, kubectl operator, and the Openshift Console due to the absence of `olm.bundle.object` properties https://olm.operatorframework.io/docs/tasks/creating-an-index/ 

AC: 

A design exists and is implemented for the best way to handle populating `olm.bundle.object` properties in catalogs.