Node owners can fetch PII for Jumio verified accounts

Previously the verification info returned from Jumio (ID scans urls, liveness image urls, name, dob, address, etc) was being directly stored in userMetadata as part of the Jumio callback. This was changed in #105 so that the info is no longer being directly stored, but the `JumioTransactionID` (which appears to be a Jumio scan reference) is still being stored in the userMetadata here: https://github.com/bitclout/backend/blob/07676b2a874d7c37dd3a1bc8f4679f5621b46cbf/routes/verify.go#L805

It seems [this Jumio API](https://github.com/Jumio/implementation-guides/blob/master/netverify/netverify-retrieval-api.md#retrieving-details) can be used to fetch this same info given a scan reference and Jumio API secret, both of which the node owners have access to. Is this intentional?

Since it is the node owner providing the funds for this verification bonus (right now not aware of anyone outside of bitclout.com / identity.bitclout.com doing this) I suppose it is within their rights to be able to look up this information, but I would like to hear about if the intent is for this to be a temporary measure to help debugging abuse while this rolls out or something that is intended to stick around long term (for KYC compliance or other reasons). Both seem potentially reasonable, but In either case it seems like this should be called out as part of the verification flow, or at the very least on https://docs.bitclout.com/faq/privacy-and-security so that users are aware of the transaction they are making.

As it stands right now I feel a bit uncomfortable verifying my account without this being addressed, and feel especially uncomfortable about onboarding users and recommending they verify, be it directly on bitclout.com or as part of any app I might build on the network that wishes to take advantage of "gas on the fire" bonus to attract new users.

Also. I considered opening this as a CIP discussion but it seems worth first understanding the intent of what has already been implemented before diving into any specific discussions about changes or alternatives.

Start with routes/verify.go around line 805, compare the change in #105, and read the linked privacy FAQ and Jumio retrieval API. Confirm whether retaining JumioTransactionID intentionally permits node-owner access; done requires an explicit decision and corresponding verification-flow or privacy documentation.

Written by the indexing model from the issue text.