Update auxiliary.sh gpg calls with calls to python scripts

[diveshuttam]

pgpg/src/auxiliary.sh

Line 34 in d108baf

gpg --version | head -n 1 | cut -d" " -f3

pgpg/src/auxiliary.sh

Line 42 in d108baf

secret_keys=$(gpg --homedir="$gnupghome" --list-secret-keys --with-colons | grep '^sec' | cut -d: -f5)

pgpg/src/auxiliary.sh

Line 45 in d108baf

keyinfo=$(gpg --homedir="$gnupghome" --list-keys --with-colons $key_id | grep '^pub:u:')

pgpg/src/auxiliary.sh

Line 69 in d108baf

FPR=$(gpg --list-keys --fingerprint --with-sig-check --with-colons $GPG_KEY | grep '^fpr:' | cut -d: -f10 | head -n 1)

pgpg/src/auxiliary.sh

Line 74 in d108baf

key_details=$(gpg --list-keys --with-colons $GPG_KEY)

pgpg/src/auxiliary.sh

Line 101 in d108baf

[[ -n $(gpg --list-secret-keys --with-colons $key_id 2>/dev/null) ]]

pgpg/src/auxiliary.sh

Line 113 in d108baf

fingerprint=$(gpg --with-colons --fingerprint $key_id | grep '^fpr' | cut -d: -f10 | head -n 1)

[diveshuttam]

Relevant link for vesrion check
https://www.gnupg.org/documentation/manuals/gpgme/Engine-Version-Check.html#Engine-Version-Check

[dashohoxha]

Maybe we can skip this one too.

[diveshuttam]

added version using gpgme in #86

[dashohoxha]

It was not necessary.
Actually the best thing would be to replace auxiliary.sh with auxiliary.py, instead of replacing single gpg occurrences. But this is useful only if you have a program that is 100% Python.