return the query fingerprint id in hexadecimal rather than int64

[florence-crl]

discussed with @sravotto in this internal slack thread

Currently, when you pull query info using the metrics-exporter it gives the fingerprint id in int64 format. In the DB and Cloud Consoles, the Statement Details page URL also uses the fingerprint id in int64 format. So you can use the fingerprint id from the metrics-exporter to open the Statement Details page for a particular query.

If this feature request to the DB Console, Use hexadecimal Statement Fingerprint ID in the URL of the Statement Details page #91875 - is implemented. You will not be able to use the int64 fingerprint id from the metrics-exporter in the URL of the Statement Details page.

When 91875 is implemented, please modify the metrics-exporter to return the query fingerprint id in hexadecimal rather than int64.