Revise the arguments for `to_parquet` method calls

[nrs23]

we use this pattern when writing to parquet in our our different pipeline stages:

    future: dd.Scalar = ddf.to_parquet(
        Path(outfile),
        version='2.6',
        allow_truncated_timestamps=True,
        write_index=False,
        compute=False,
    )

Do we need to be using version with a static version number? Do we need truncated timestamps?

[m4gpi]

This version is for the parquet files, see https://arrow.apache.org/docs/python/generated/pyarrow.parquet.ParquetWriter.html

version{“1.0”, “2.4”, “2.6”}, default “2.6”
Determine which Parquet logical types are available for use, whether the reduced set from the Parquet 1.x.x format or the expanded logical types added in later format versions. Files written with version=’2.4’ or ‘2.6’ may not be readable in all Parquet implementations, so version=’1.0’ is likely the choice that maximizes file compatibility. UINT32 and some logical types are only available with version ‘2.4’. Nanosecond timestamps are only available with version ‘2.6’. Other features such as compression algorithms or the new serialized data page format must be enabled separately (see ‘compression’ and ‘data_page_version’).

[m4gpi]

Truncating timestamps seems sensible since we don't really care too much about timestamp precision below minutes.