[skip ci]

Similar to the aleph file created for builds of FCOS based on ostree
commit inputs, this adds an aleph file builds based on container image
inputs.

the container image metadata

Fixes some of the labels in the aleph file. Calling `ostree container
image metadata` also requires the target image reference to be only
the container image and tag (ie. without the signature verification
type and remote).

Apply key sorting when using `json.dump`. Prevent double dict
query and string buffer creation.

Refactor the code in the deploy stage to create a separate aleph
stage. A new stage prefered as both the org.osbuild.ostree.deploy
and org.osbuild.ostree.deploy.container stages need an aleph file.
Aleph files are also a coreos specific feature, which is why a
separate stage is beneficial.

Create a symlink between the `.aleph-version.json` and
`.coreos-aleph-version.json` files to allow for backward compatibility
with CoreOS.

This commit allows the target imgref to be found automatically from
the deployment root's origin file. If the deployment is not specified
in the mpp.yaml file, this stage will be able to populate the aleph
file on the assumption that there is only one deployment.

This commit makes the code more clear by refactoring the part extracts
the deployment type and imgref from the origin file into a separate
function. This function was implemented as an ostree tool such that
other stages can also utilize it. Several other minor changes were also
made to clean up the code