[Voting] Case insensitivity attribute for flags

[GZTimeWalker]

Giving flags the possibility to be validated in a case-insensitive form may be useful for some challenges.

NOTE: This feature introduces possible database modifications that will make it dangerous to downgrade after an upgrade

---

Please vote for your level of interest by adding a reaction to this comment:

• 👍 Wanted: This is a feature you’d like to see added.
• 🤔 Considered: This is a feature you’d be okay with, but it’s not essential.
• 👎 Not Needed: This is a feature you think is unnecessary.

[GZTimeWalker]

After concluding our discussion, we've decided that this feature is unnecessary for the following reasons:

1. For challenges where the case will be broken, a GUID or team hash can be used to generate a hexadecimal string. The specific answer format can be defined in the challenge description, player should use the specified case to submit.

2. In terms of potential variations, GUID offers the most possibilities, followed by team hashes, with leet being the least possibilities.

3. If there's a strong need to customize the flag format, I recommend using the following basic logic when generating dynamic attachments or content:

   flag = gzctf_flag
   seed = hash(flag)
   
   random.seed(seed)
   
   # use seed & random to build another task
   # also the key to encrypt real flag
   task_flag = ...
   enc_flag = encrypt(flag, key=task_flag)
   
   # so you can use task_flag to generate 
   # any special challenges you need
   challenge = ...
   
   # finally, give players both enc_flag and challenge
   # once they solve the challenge, they get the real flag
   print(enc_flag)
   print(challenge)