Add additional database functions.

[Nick Pope]

I propose adding some additional database functions:

• Random -- generate random numbers in the range [0.0, 0.1).
• Truncate -- round number towards zero. (SQL function is TRUNC, but Trunc is used for date truncation in Django.)
• Log2 and Log10 -- simple logarithm functions without needing to provide the base.
• ACosh, ASinh, ATanh, Cosh, Sinh, and Tanh -- hyperbolic functions.
• BitLength and ByteLength -- length of string in bits and bytes, complement to Length which is character length.

[Nick Pope]

​PR

[Mariusz Felisiak]

I'm not sure if it's worth adding extra database functions:

• Log2 and Log10 can be achieved with proving base to Log so I'm against them,
• hyperbolic functions are supported only on PostgreSQL 12+, we need to emulate them on other DBs, it's not worth, IMO,
• BitLength and OctetLength will probably not work on Oracle.

Truncate and Random sound reasonable.

[Mariusz Felisiak]

I think we need to decide at what point we say enough is enough here, and recommend users create their own functions like we did with template tags. For me hyperbolic functions cross that line. You can start a discussion on DevelopersMailingList if you don't agree. Personally I've never used any of proposed database functions.

[Nick Pope]

Will you still take Random and Truncate?

In the case of Random there is also a nice bit of simplification:

​https://github.com/django/django/commit/c8913d41e74859747893dc21356a1fb6906c56e9

[Mariusz Felisiak]

Random() is already there (as an expression) so we can change it to a function and promote in docs, I'm just not sure why we change its behavior.

Truncate() can be confused with Trunc() for dates/datetimes, and we can achieve the same by using Cast(..., models.IntegerField()) so I don't think it's necessary.