There should be a way to limit the transaction timeout

When clients start a transaction, they can give a custom timeout for the transaction. If a client uses a really long timeout, then crashes and never commits or invalidates, then this will remain an active transaction forever. In some use cases, it is therefore desirable to impose a system-wide limit on that timeout.

I am proposing to add a new property data.tx.max.timeout to the configuration. This can be optional, but if set, it limits the custom transaction timeout for startShort(int timeout).