documentation for Pgp module needs to be updated

[zhisme]

Environment

Provide at least:

• Gem version 1.10.3

Expected Behavior

List keys function documentation outdated
private and trust should be added to the example list

Actual Behavior

[34] pry(main)> IOStreams::Pgp.list_keys.first.keys
=> [:private, :key_length, :key_type, :date, :key_id, :email, :name, :trust]

Pull Request

• Consider submitting a Pull Request with a fix for the issue.
• Or, even a Pull request that only includes a test that reproduces the problem.

[zhisme]

also for further improvements I think key_info part should be updated at least with example, what expected input arguments, I mentioned them in #9 (comment)

and for more clear solution, I propose to keep the same output structure for data in both key_info and list_keys
so those should be equal

[35] pry(main)> IOStreams::Pgp.list_keys.first.keys
=> [:private, :key_length, :key_type, :date, :key_id, :email, :name, :trust]
[38] pry(main)> IOStreams::Pgp.key_info(key: key).first.keys
=> [:private, :key_length, :key_type, :date, :key_id, :email, :name]

and why key_info for key returns an array? I expect it to be a simple hash.
let's discuss and I can propose PR for that

[reidmorrison]

I think the reason it returns an array is that for a "single" supplied pgp ascii key it can actually return multiple keys. This is often used to publish multiple keys in a single file, often with different expiry dates.

[reidmorrison]

As for list_keys returning trust, which key_info does not, that is what GnuPG returns for those calls. The same code is called to parse the output from GnuPG from both calls, and trust is only returned when it is returned by GnuPG.