When tagging the apertis/1.1.1d-0+deb10u2 release `git-buildpackage`
ended up misdetecting the proper orig tarball and generated a new one
using `git archive` instead, which is what ended up in the
`pristine-lfs-source` branch and then on OBS and on the APT archives:

https://gitlab.apertis.org/pkg/target/openssl/-/jobs/225652

The MR below should prevent this from happening again:

infrastructure/apertis-docker-images!109

However, the current situation breaks the release pipeline, since the
discrepancy between the proper orig tarball and the one already in
the `pristine-lfs-source` branch cause the import to fail:

https://gitlab.apertis.org/pkg/target/openssl/-/jobs/335041#L170



To address this, align the `pristine-lfs` branch to what we actually
ended up releasing as the `openssl_1.1.1d.orig.tar.gz` tarball, even if
it's not really the upstream one coming from Debian.

At the same time, stash the proper orig tarball under a different name,
so we can later re-align to the Debian provided one while avoiding
ambiguities for downstreams.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The pristine-lfs branchs is meant to only ship the orig tarballs, in
their packed form to fully preserve them. The unpacked sources ended
up here due to a bug during the original import.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>