Tighten max table entries when parsing and evaluating ICC curves

We have some assumptions elsewhere in the code that hinge on this
being smaller than 2^24.

This will make parsing fail if we are given more than ~16 million
table entries in the profile and makes sure profiles given to us
conform to that limit.

This limit may impact some fringe WebP images in Chromium; see
linked bug for more details.

Bug: b/492744328
Change-Id: I4ca302b490021e2276a55f949f36125dab44196d
Reviewed-on: https://skia-review.googlesource.com/c/skcms/+/1187536
Reviewed-by: Florin Malita <fmalita@google.com>
Auto-Submit: Kaylee Lubick <kjlubick@google.com>