Version condition caching lowercases version string to compare against

[Ortham]

This is not correct behaviour, as semver states that

identifiers with letters or hyphens are compared lexically in ASCII sort order

so case should be preserved. This is unlikely to cause issues in reality as it's a small corner case, but good fixes would be:

• Don't cache conditions case-insensitively. Simple, but increases the chance of false negatives when checking the cache.
• Parse conditions into data structures that can provide per-token granularity when checking equality, so that version strings can be compared case-sensitively while the rest of the string is compared case-insensitively. A lot more work, but better design than how conditions are currently handled.

[Ortham]

This was initially done by case-sensitive condition caching in 2c079731a5482832c44f84bf2278a8a5a905af23, then by more granular caching introduced as part of loot-condition-interpreter in 1c025a4fba60208086bbfbc87cb77ed41ada362f.