python-keyring patches are not up to standard

[Jim Somerville]

Brief Description
-----------------
The 11 patches in stx/integ/security/python-keyring/python-keyring have no git headers on them, so we have no idea where they came from or even what they are supposed to be doing or fixing. This is especially bad given that it is a security package.

Somebody in Wind River should do some archeology on them and get appropriate git headers on them.

<Rest of template left out because it is not applicable>

[Ghada Khalil (gkhalil)]

screening: not gating; code cleanup, should be done, but won't hold up any stx release

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/integ/+/811029
Committed: https://opendev.org/starlingx/integ/commit/de2af4d74df8d7b1d37d07d5f7dbc990e2fda390
Submitter: "Zuul (22348)"
Branch: master

commit de2af4d74df8d7b1d37d07d5f7dbc990e2fda390
Author: Yue Tao <email address hidden>
Date: Sun Sep 26 17:32:41 2021 +0800

    Add debian package for python-keyring

    The upstream commit 1e422ed of python-keyring moved non-preferred
    keyring backends to separated package "keyrings.alt", so adding the
    keyrings.alt and porting the patches related to non-preferred
    keyring backends to keyrings.alt.

    Patches are not up to our standard. Bringing them up to standard
    is future work, tracked by:

    https://bugs.launchpad.net/starlingx/+bug/1950506.

    Related-Bug: 1950506

    Building successfully.

    Installing python3-keyrings.alt, python3-keyring and the dependence
    package tsconfig successfully.

    Booting up ISO successfully on qemu.

    Story: 2009221
    Task: 43438

    Signed-off-by: Yue Tao <email address hidden>
    Change-Id: I4b70927709f0cc968e32af1d0e2a9402f47b2fe9