Add configurable SQLite special cases for MA0042 and MA0045

[meziantou]

SQLite async recommendations in MA0042/MA0045 were previously hardcoded for SqliteConnection.CreateCommand(). Because SQLite types are not sealed and derived implementations may provide meaningful async behavior, this change makes SQLite exceptions configurable and extends the coverage to the commonly reported command execution methods.

What changed

• Added a new analyzer option: MA0042.enable_sqlite_special_cases (default: true).
• Gated all SQLite-specific behavior behind this option for both MA0042 and MA0045.
• Expanded SQLite special-case method coverage to:
  • SqliteConnection.CreateCommand()
  • SqliteCommand.ExecuteNonQuery()
  • SqliteCommand.ExecuteScalar()
  • SqliteCommand.ExecuteReader()
• Updated MA0042 and MA0045 documentation with the expanded SQLite behavior and configuration.
• Added regression tests for:
  • MA0042 and MA0045 no-diagnostic behavior when special cases are enabled.
  • MA0042 and MA0045 diagnostics when MA0042.enable_sqlite_special_cases = false.
  • Metadata-based API contract validation that SqliteConnection.CreateCommand() returns SqliteCommand.

Notable implementation detail

Invocation-level method caching in DoNotUseBlockingCallInAsyncContextAnalyzer was adjusted so SQLite-special-case methods are not cached as permanently "no async equivalent". This avoids stale behavior when the new configuration is toggled.

Validation

• Ran targeted SQLite MA0042/MA0045 tests (including option-disabled scenarios and PEReader contract test).
• Regenerated documentation with DocumentationGenerator.
• Ran full solution tests (Meziantou.Analyzer.slnx).

Fix #1121