once bootc is in RHCOS, the priority for 4.16 should be to have a backend so that if a bootc enabled image was supplied, MCO could handle it.

this will entail mimicking the current setup for rpm-ostree in pkg/daemon/rpm-ostree.go.

One outstanding question is will we need (or should we use) go bindings similar to rpm-ostree? cc walters@redhat.com

Discussed the need for go binding with the team during the Image Mode Convergence Mini Scrum. Discussion result summarized below: 

• Go bindings for bootc is not a must and, as a result, will be outside of the scope of this epic and will not be implemented. The main purpose of creating go bindings for rpm-ostree/bootc is to have an easier way to parse the created json and to read the status of rpm-ostree/bootc. This can be done via creating a simple wrapper function inside of the MCO. It will make sense to separate it out to a standalone helper/library in the future when the demand raises, but is a non-goal for now. 

Done when:

• We can trigger a build with bootc (and without rpm-ostree).
• This excludes extensions and kargs