Hash user snowflakes

[jftanner]

Feature

Rather than storing user IDs directly, the bot should store hashed versions of them.

Reasons for Implementing

The reasons are simple:

• The snowflake could be considered PII, and thus should not be stored unless absolutely necessary.
• The bot only needs to fetch/update user records when requested by the users. No reverse-lookup is necessary.

Ideas & Details

Use a cryptographic hash to generate a unique document ID for each user settings document.
The hash (and therefore the document ID) can be recalculated whenever the document is needed.

[Tanndev-CI]

This issue is resolved in version 2.4.0-beta.1

[Tanndev-CI]

This issue is resolved in version 2.4.0