New CSV report for RANGES work

[mkoo]

          Tentative list of fields to include in CSV:

-GUID
-catalog number
-simple identifiers
-part names
-county - asserted
-state - asserted
-specific locality
-verbatim date
-age (from flat)
-total length (from flat)
-tail length (from flat)
-hind foot with claw (from flat)
-ear (from notch) (from flat)
-weight (from flat)
-reproductive data (from flat)

rest are not in flat so hopefully Dusty can retrieve from JSON blob of attributes and include as part of the CSV
-ear (from crown)--
-crown-rump length
-unformatted measurements (this is text)
-life stage (yes this is a controlled vocab)

Originally posted by @mkoo in #8382 (comment)
(sorry this needs a new issue)

[mkoo]

More notes:
metadata for attributes to CSV -- > , <attribute-type+ attribute_units>, <attribute-value+ attribute_date>, <attribute-value+ attribute_determiner>, etc

Example for attribute-type= length: cols are:
-length (which has the attribute_value), length_units, length_date, length_determiner etc

The attribute metadata will be in the CSV but as columns so user can delete or hide as desired

Typical duplicate attribute_type handling will be to duplicate row with the record. (right?)

[dustymc]

This is done as mvz_ranges_csv.

I'm not at all sure that I've correctly understood the needs so I just added the record attribute summaries from flat, and the rest using the same function I use to cache them in FLAT. That should at least be enough to support a conversation, let me know when/if something needs adjusted.

We can also discuss the record limit if necessary, let me know details if pulling more than 20K records at a time becomes a bottleneck.

[Jegelewicz]

@jebrad will probably want to use this report eventually.