Coordinate getpubkeys() requests to prevent deanonymizing attacks
From discussion in !1090 (merged), Lox pubkeys should be refetched every day that Tor browser is open and/or upon opening Tor browser if it has been longer than that. This will do the work of checking for a change in Lox public keys, that are required to make successful Lox requests. In order to prevent a user from deanonymizing themselves by making a request to update a credential that was generated with an old key immediately prior to another Lox request, it is advisable to block other Lox requests until some time after a pubkey update has succeeded. Instead of having each Lox related request fetch the pubkeys, it probably makes more sense to check whether or not pubkeys have been fetched recently and attempt to perform the request. If the request fails, pubkeys could be refetched with the same delay between subsequent Lox requests. See also: #42456 #42502