fix: enable uint64 support

[e-dard]

This PR enables uint64 support in InfluxDB. This means that you can write unsigned integers into the database. To differentiate between unsigned integer values and signed integer values, use the u suffix.

Example:

influx write -o edd -b edd  "cpu,region=west balance=-232i,space=23432u

Where balance is a regular signed integer, and space is an unsigned integer.

Within the TSM storage engine both signed and unsigned integers are compressed in the same way. You cannot mix signed and unsigned integers within the same series, e.g., you cannot do this:

influx write -o edd -b edd  "cpu,region=west space=23432u
influx write -o edd -b edd  "cpu,region=west space=100i

The approach here is temporary. We should make this change permanent by removing all the code that allows uint64 to be disabled. #15711 tracks that work

[jsternberg]

Yea, this makes sense. The only reason it is not enabled automatically is because we wanted to add uint64 support to the rest of the 1.x products before enabling it in 1.x. Since this only applies to 2.0, it makes sense to enable the support by default.