stabilization tracker: `bootc image copy-to-storage`

Original PR: https://github.com/containers/bootc/pull/620

This issue tracks the stabilization of `bootc image`, which currently just has one subcommand `bootc image copy-to-storage`.

## Rationale

We want to make it ergonomic and convenient to operate on the booted host image via e.g. `podman`. Today usage of podman defaults to operating on `/var/lib/containers`, a distinct mutable store.

Having the ability to conveniently copy the image to the booted storage aids with https://containers.github.io/bootc/booting-local-builds.html

## Concerns

- Longer term, we want to unify bootc and podman storage; but perhaps `copy-to-storage` can become a no-op
- Would it be better to try to instead expose an API to *read* from the bootc storage, and wrap that in a CLI?

Revisa primero el PR #620 original y el punto de entrada actual `bootc image copy-to-storage`. Compara su comportamiento con la documentación de booting-local-builds y el objetivo establecido para el almacenamiento de Podman. El trabajo se considera terminado cuando exista una dirección de estabilización acordada —si se conserva, se reemplaza o se convierte el comando en un no-op—, junto con un alcance de implementación y un plan de validación.

Escrito por el modelo de indexación a partir del texto del issue.