Unbreak the gpg state module

[lkubb]

What does this PR do?

• Makes the gpg state module correctly report success and failure and honor test=true.
• Makes gpg.receive_keys detect when a key could not be imported due to a missing user ID.
• Makes gpg.receive_keys detect when a key could not be imported due to an unreachable keyserver.
• Makes gpg.absent work with user/gnupghome.
• Makes gpg.delete_key work with gnupghome.
• Fixes documentation regarding what needs to be passed in as name/keys, namely a key ID. Anything else will be detected as absent currently.

What issues does this PR fix or reference?

Fixes: #65169
Fixes: #63153
Fixes: #63156
Fixes: #63144
Fixes: #63159
Fixes: #62129

Previous Behavior

Very broken. See linked issues for details.

New Behavior

Makes the state module work as intended, apart from trust management with gnupghome, which is still broken since gpg.trust_key does not support it currently.

Merge requirements satisfied?

• Docs
• Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.html
• Tests written/updated

Commits signed with GPG?

Yes

[OrangeDog]

(while you're deep in the gpg state, do you fancy adding a PR for 59783 too?)

[lkubb]

@twangboy Mind taking a look at this? The gpg state module does not deserve that label as it is sadly.

[lkubb]

Is there any chance of getting this merged soon? This fixes basic functionality and I have several dependent PRs that I would like to get into 3007.0 as well. :)

[github-actions]

💔 All backports failed

Status	Branch	Result
❌	3006.x	Backport failed because of merge conflicts You might need to backport the following PRs to 3006.x: - Clean up new module unit tests - Add test for issue 65169 - Backport fix for delete_key - Backport more meaningful tests - Add tests for issue 63159 - Fix gpg.receive_keys returns success on failed import - Add tests for state module and issue 63144

Manual backport

To create the backport manually run:

backport --pr 63162

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details