fix(mcp): classify compound CREATE routines as DDL

[Stiwar0098]

Bug Description

MCP activity currently classifies MySQL/MariaDB compound routine DDL such as \CREATE PROCEDURE ... BEGIN ... END\ as \unknown\ because semicolons inside the routine body trip the generic multi-statement guard.

Steps to Reproduce

1. Run a MySQL/MariaDB statement like:
   \\\sql
   CREATE PROCEDURE tabularis_fix_test_proc()
   BEGIN
   SELECT 1 AS ok;
   END
   \\\
2. Check the MCP activity table entry for the query kind.

Expected Behavior

The activity entry should classify the compound routine creation as \ddl\.

Actual Behavior

The activity entry is classified as \unknown\.

Proposed Fix

Detect compound \CREATE PROCEDURE\, \CREATE FUNCTION\, \CREATE TRIGGER\, and \CREATE EVENT\ statements before the generic trailing-statement guard, while keeping obvious trailing payloads fail-closed as \unknown\.

Verification

• Fresh-context reliability review: no PR-opening blockers after adding fail-closed payload coverage.
• Builds/tests were not run because the maintainer explicitly requested not to run a build.