sqlite: backport targeted security fixes for issue #3904

[jmahotiedu]

Summary

• targeted SQLite src/* security backports for issue Unfixed vulnerabilities in sqlite due to out-of-date source version #3904 (without a full SQLite version rebase)
• added commit applicability/disposition matrix in sqlite/SECURITY_PATCHSET_3904.md
• applied parser/planner/rename/integrity hardening updates in:
  • sqlite/src/alter.c
  • sqlite/src/build.c
  • sqlite/src/expr.c
  • sqlite/src/pragma.c
  • sqlite/src/resolve.c
  • sqlite/src/select.c
  • sqlite/src/sqliteInt.h
• added targeted regression cases in tests/sqlite_bugs.test/t01..t05.{sql,expected}

Notes on Applicability

• 1e9c47be... marked already_present
• generated-column-specific commits 522ebfa... and 926f796... marked not_applicable on this baseline (generated-column symbols/features are absent in this tree)
• manual semantic adaptations documented for diverged hunks (380969..., 396afe...)

Verification

Executed in Linux-native environment (Ubuntu WSL clone):

• cmake -S . -B build -DCOMDB2_TEST=1 ?
• cmake --build build -j $(nproc) ?
• cmake --build build --target test-tools -j $(nproc) ?
• cd tests && make sqlite_bugs ? (TESTID=97401)

Additional check:

• cd tests && make cdb2api fails in this environment at existing t30.req setup with:
  • STRING DEFAULT OPTION SCHEMA MUST BE A VALID DATETIME: d1
  • reproduced in TESTID=88155 and TESTID=24502

Refs: #3904