fix(mariadb): drop MySQL-only log_error_verbosity, reclassify secure_timestamp as static

[weicao]

Summary

addons/mariadb/config/mariadb-config-effect-scope.yaml lists two parameters that are invalid for MariaDB. Both were runtime-confirmed on mariadb:11.4 (2026-07-06).

1. log_error_verbosity — MySQL-only, crash-class (removed)

log_error_verbosity is a MySQL 5.7+ system variable that does not exist in MariaDB. It was listed under dynamicParameters, so a reconfigure would persist it into the engine config. On next restart mariadbd rejects it:

$ mariadbd --log_error_verbosity=3 --verbose --help
[ERROR] mariadbd: unknown variable 'log_error_verbosity=3'   # exit rc=7

This is the same failure class the addon already documents for rpl_semi_sync_master_wait_for_slave_count (removed in a prior change with the note "MariaDB 11.4 does not recognize the MySQL-specific variable ... CrashLoops the engine container on first startup"). MariaDB uses log_warnings (already in the list) for verbosity. Fix: remove log_error_verbosity.

2. secure_timestamp — read-only variable, mis-classified as dynamic (moved to static)

secure_timestamp is a read-only MariaDB variable (information_schema.SYSTEM_VARIABLES.READ_ONLY = YES); it can only be set at startup:

$ mariadb -e "SET GLOBAL secure_timestamp='YES';"
ERROR 1238 (HY000): Variable 'secure_timestamp' is a read only variable

It was under dynamicParameters, so the Configure controller would attempt SET GLOBAL and fail. Fix: move it to staticParameters so a reconfigure of it correctly triggers a restart.

Not changed (verified NOT bugs)

While auditing I also checked two params from the same area and confirmed they are not defects on MariaDB 11.4, so they are intentionally left as-is:

• sql_log_bin — READ_ONLY = NO; SET GLOBAL sql_log_bin=1 succeeds on MariaDB (unlike MySQL 8, which removed the global). Genuinely dynamic.
• wsrep_slave_threads — exists as a built-in variable even without the wsrep provider loaded, so it does not crash non-galera topologies (it is inert there). A cross-topology scope-cleanliness nit, not a correctness bug.

Tests

reconfigure_persisted_alpha86_spec.sh: new guard group asserting log_error_verbosity is absent everywhere and secure_timestamp is classified static, not dynamic. Full mariadb suite: 666 examples, 0 failures.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 0.00%. Comparing base (554fd84) to head (6e038fc).

Files with missing lines	Patch %	Lines
...ipts-ut-spec/reconfigure_persisted_alpha86_spec.sh	0.00%	19 Missing ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #3070   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files        144     144           
  Lines      23053   23072   +19     
=====================================
- Misses     23053   23072   +19     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[weicao]

rebase 到 main 554fd84 + re-author 为 Magnus magnus@apecloud.com + 移除 AI 署名 trailer。内容零变化（#3030/#3020 已在 merge base 内）。

[weicao]

Superseded by #3276. This PR's current head 6e038fc is included in the consolidated candidate 7978812; further review and testing should use #3276.

[weicao]

Reopened per owner direction after rolling back the consolidated PR #3276. This PR is again an independent review and validation unit.

[weicao]

This changes the rendered ComponentDefinition spec.configs[].reconfigure content while keeping chart version 1.2.0-alpha.26. On released KubeBlocks v1.0.0 that field is immutable, so same-name upgrades can be rejected and leave the ComponentDefinition unavailable.