Ten MariaDB configuration parameters' documentations are inconsistent with the implementation

We discovered several discrepancies in the documentation for MariaDB configuration properties: https://mariadb.com/kb/en/server-system-variables

1. `max_write_lock_count`: The documentation states that the minimum value is `0`. However, if set to `0`, MariaDB automatically adjusts it to `1`.
2. `transaction_alloc_block_size`: The documentation specifies a maximum value of 4294967295. However, if users set a value greater than 128M, MariaDB automatically changes it to 128M.
3. `mrr_buffer_size`: The maximum value in the documentation is `2147483648`. When users set it to this value, MariaDB reduces it to `2147483647` (the maximum value minus 1).
4. `transaction_prealloc_size`: The documentation specifies a maximum value of `4294967295`. However, any value greater than `128M` is automatically adjusted to `128M` by MariaDB.
5. `net_read_timeout`: No maximum value is listed in the documentation, but MariaDB enforces the same maximum constraint as MySQL: `31536000`.
6. `net_write_timeout`: Similar to net_read_timeout, the documentation lacks a maximum value, but MariaDB enforces the same constraint of `31536000`.
7. `read_buffer_size`: The documentation states a minimum value of `8200`. However, if set to `8200`, MariaDB changes it to `8192`.
8. `connect_timeout`: The documentation does not specify constraints. However, if users set a value less than `2`, MariaDB adjusts it to `2`, consistent with MySQL's behavior.
9. `debug_no_thread_alarm`: When users set `debug_no_thread_alarm` in the `my.cnf`, the mariadb crashes due to `unknown variable error`.
10. `transaction_read_only`: The documentation is inconsistent, in [transaction_read_only detail page](https://mariadb.com/docs/server/ref/mdb/system-variables/transaction_read_only/), it states command line and configuration file are not supported. However, in [Server System Variables](https://mariadb.com/kb/en/server-system-variables/#transaction_read_only), users are allowed to use command line and configuration file to set this variable. Additionally, if users set `transaction_read_only=ON` in the configuration file, the mariadb crashes.

We recommend updating the documentation to reflect the actual constraints imposed by the MariaDB implementation for each property. Providing accurate information will help users avoid confusion and configure their systems correctly.