Added Bundle Image

[yuriolisa]

Resolves #1823

[jaronoff97]

How is this going to be used in CI?

[pavolloffay]

How is this going to be used in CI?

The same question, what are we planning with the bundle image? Who is consuming it? Is the plan to publish is af part of the #1879 (cc) @iblancasa )

@IshwarKanse are you planning to use the bundle image?

[IshwarKanse]

@pavolloffay @jaronoff97 This PR adds steps to build the catalogsource image using the operator bundle image. We were planning to use #1823 as part of our CI in which we build the images on a nightly basis and update the index and use another job which runs e2e tests consumes the updated builds via the catalogsource. However we decided to add a job which builds the latest bundle, installs it using operator-sdk and use it to run e2e tests.

Considering our efforts to build and publish the operator bundle outlined in #1879, it would be advantageous to also build and publish the catalogsource image. CatalogSources are widely recognized and accepted as a distribution mechanism for operators, providing compatibility and allowing for usage in disconnected environments. By utilizing the catalogsource in conjunction with imageContentSourcePolicy, we can use mirrored images without altering the references to the operator images in the CSV. This approach offers a more streamlined and standardized installation and management process, as users can leverage the published CatalogSource index image instead of manually configuring and running the operator bundle with operator-sdk.