WT-8876 will introduce a default write_timestamp_usage of ordered. As we only set write_timestamp_usage on test runs, we should prepare for the change by setting the usage in all circumstances.

Additionally we may want to set the sizeStorer to a usage of `none`.

Some background: with WT-8876, WT's behavior on a MDB release build w.r.t: write_timestamp_usage will be to:

• default to `ordered` if one is not specified. This is an in-memory setting and not persisted.
• If an violation is found: log an error
• succeed the transaction

This keeps the behavior as we have it today. Assuming our existing test coverage is complete (where these assertions fail tests), we expect no log lines to emitted.

After confirming there are no new log lines, WT can change behavior to fail commits if the write_timestamp_usage assertion isn't satisfied.

This ticket should also take care in setting the write_timestamp_usage back to none (or disabling its assertion/verbose settings) when shutting down with a downgraded FCV. Generally speaking, everytime we strengthen an assertion in a new release there must be accompanying code to relax it on downgrade.