[Feature] Client Side Hamming Distance Settings for Identify Tasks

[kbstash]

Is your feature request related to a problem? Please describe.
False positives frequently occur when using the identify function with various stash-box instances. Partly I believe this is due to some bad hashes on the stash-box side which is understandable. False positives also seem to stem from the phash hamming distance that is set on the server side. In my case I would only like to pull exact matches into my db when using identify. While I understand one of the strengths of perceptual hashing is matching on images with some distance, I believe that allowing the user to decide the distance would be a better use experience.

Describe the solution you'd like
Allow client side hamming distance to be set per stash-box in the identify settings.

Describe alternatives you've considered
Adding a similar setting to the ad hoc tagger settings might also be useful. That interface feels more suited to setting varying distances as the user is validating the matches before saving in most cases.

Additional context
I believe fansdb recently made the server side change to increase the hamming distance from 0. This created well over 1000 false positives in a single identify task. It feels like filling local stash instances with high numbers of false positives can eventually lead back to those bad matches being submitted to stash-box instances if users aren't being diligent.