Keep Oracle procedure declarations in one statement

[RamiNoodle733]

Summary

Fix sqlparse.split() incorrectly splitting Oracle-style CREATE PROCEDURE ... AS declarations at semicolons that appear before the procedure's BEGIN body.

The splitter now tracks when it is inside a CREATE PROCEDURE, keeps declaration semicolons inside that statement, and clears that state when the procedure's outer END closes. This preserves normal splitting for a statement that follows the completed procedure.

Added focused regression coverage using the maintainer's simplified reproducer from #692, plus a second case confirming a following SELECT is still returned as a separate statement.

Fixes #692

Checklist

• ran the tests (pytest) - the automation environment cannot check out the repository; the upstream workflow is currently awaiting external approval before jobs can run
• all style issues addressed (ruff) - not available locally; the upstream workflow is currently awaiting external approval before jobs can run
• changes are covered by tests
• documentation is not needed for this parser bug fix

AI assistance was used to inspect the issue and repository guidance and to implement the focused splitter-state change.

[RamiNoodle733]

Closing this as a duplicate of the earlier active #858, which addresses the same #692 Oracle procedure-splitting root cause and already includes full local validation. Keeping the older PR avoids overlapping implementations.