[BUG] Human Checker needs to lock when something is calling it

[bee-san]

The human checker runs twice here:

ares -t '61BVLSFfA8QwcDnjxY47PfQ3FBWAhoANQ5yfRtoUptRS'
🕵️ I think the plaintext is Internet Protocol (IP) Address Version 4.
Possible plaintext: '192.168.0.1' (y/N):
🕵️ I think the plaintext is Internet Protocol (IP) Address Version 4.
Possible plaintext: '192.168.0.1' (y/N):
y
y

🥳 Ares has decoded 164 times times.
If you would have used Ciphey, it would have taken you 32 seconds

The plaintext is:
192.168.0.1
and the decoders used are Base58 Bitcoin → Base32 → Base64 URL

This is because both Base64 and Base64_url (being a superset of base64) can decode it.

because Ares is multi-threaded, both threads call human checker at roughly the same time. This creates a race condition. An ideal solution would be to have a locking system to lock the human checker (only 1 input at a time), but that requires more thinking than I have right now.

This hack moves the decoders far apart. Ares executes the decoders in order (using multi-threading), which means it will decode base64 first and then base64_url last.

#172 relevant PR