Correct documentation on dump_log_write_threshold default value

* dgud/mnesia/sticky-bug/ERL-768/OTP-15979:
  mnesia: Bump protocol version
  mnesia: Introduce sync_asym_trans protocol

```erl
1> mnesia:system_info(dump_log_time_threshold).
1000
```

Looks like a missing `0`!

Remove unsupported conversions from the old protocols.
This means mnesia on OTP-R18 nodes is no longer able to connect to
OTP-22 mnesia nodes.

Add protocol conversion for old nodes and sync_asym_trans transactions.

Transactions with sticky locks could with async_asym transactions be
committed in the wrong order, since asym transaction are spawned on
the remote nodes.

See ERL-768.

If add_table_copy was called when a node was starting it deadlock
waiting for mnesia_controller, when schema was not merged.

Abort if that is the case.

If an activity function fails with an error, the stacktrace is
dropped in non_transaction function try/catch clause.
This makes debuging of errors inside a transaction really hard.

Transaction activities handle errors and exits differently, non-transaction
activities should do the same.

Adding the stacktrace to the exit reason when translating errors to exits.

This reverts commit 425889ba69b69a9b6fb14bfbef121d51b78e853a.