crypto-polygon traces table: traceid order in schema

[Phread420]

This is a minor, but annoying issue:

In the schema for the traces table, the traceid is the last column in the public data crypto-ethereum dataset, but is NOT the last column in the crypto-polygon dataset.

That prevents me from writing concise cross-blockchain queries (using, for example, UNION). It'd be awesome if the schemas for the crypto-polygon and crypto-ethereum datasets were identical.