fix: BYT-8268 - require CALL keyword at SQL level and fix related grammar issues (#38)

This commit addresses BYT-8268 by making the CALL keyword mandatory at SQL
statement level while keeping it optional at PL/SQL block level, and fixes
grammar issues that were previously hidden by optional CALL.

Changes:
1. Split call_statement into two rules:
   - sql_call_statement: CALL keyword MANDATORY (SQL level)
   - plsql_call_statement: CALL keyword OPTIONAL (PL/SQL block level)

2. Support method chaining in CALL statements:
   - CALL obj_constructor(...).method(...) INTO :var

3. Fix commit_statement to allow WRITE clause independently:
   - Previously: COMMIT [COMMENT 'text' [WRITE ...]]
   - Now: COMMIT [COMMENT 'text'] [WRITE ...]

4. Fix link_name to support qualified database links:
   - Now supports: @schema.linkname or @linkname.domain

5. Fix system_action to support multi-word actions:
   - Added: ADMINISTER KEY MANAGEMENT
   - Added: General patterns for 2-3 word actions

Why these changes:
- The optional CALL keyword caused keywords like CASCADE to be
  misidentified as procedure calls, leading to incorrect SQL splitting
- At SQL level, Oracle requires CALL keyword
- At PL/SQL block level, Oracle allows direct procedure invocation
- The fixes to COMMIT, link_name, and system_action address grammar
  deficiencies that were previously hidden by the optional CALL

Tests: All 600+ parser tests pass

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <[email protected]>

Author: rebelice

plsql/PlSqlParser.g4

@@ -178,7 +178,7 @@ unit_statement
     | truncate_cluster
     | truncate_table
     | unified_auditing
-    | call_statement // put call statement after all statements.
+    | sql_call_statement // put call statement after all statements. BYT-8268: SQL level requires CALL keyword
     ;
 
 // https://docs.oracle.com/en/database/oracle/oracle-database/21/sqlrf/ALTER-DISKGROUP.html
@@ -1335,11 +1335,16 @@ object_action
     | RENAME
     ;
 
+// BYT-8268: Added support for multi-word system actions
+// Note: Complete list varies by Oracle version, query AUDITABLE_SYSTEM_ACTIONS view for full list
 system_action
-    : id_expression // SELECT name FROM AUDITABLE_SYSTEM_ACTIONS WHERE component = 'Standard';
+    : ADMINISTER KEY MANAGEMENT  // TDE operations
     | (CREATE | ALTER | DROP) JAVA
     | LOCK TABLE
     | (READ | WRITE | EXECUTE) DIRECTORY
+    | id_expression id_expression id_expression  // 3-word actions (ALTER AUDIT POLICY, etc.)
+    | id_expression id_expression  // 2-word actions (ALTER ASSEMBLY, CREATE TABLE, etc.)
+    | id_expression  // Single-word actions
     ;
 
 component_actions
@@ -5607,7 +5612,7 @@ statement
     | case_statement
     | sql_statement
     | pipe_row_statement
-    | call_statement // put call statement after others.
+    | plsql_call_statement // put call statement after others. BYT-8268: PL/SQL level allows optional CALL
     ;
 
 swallow_to_semi
@@ -5687,8 +5692,16 @@ return_statement
     : RETURN expression?
     ;
 
-call_statement
-    : CALL? routine_name function_argument? (INTO bind_variable)?
+// BYT-8268: Split into two rules for different contexts
+// SQL level: CALL keyword is MANDATORY to prevent misidentifying keywords like CASCADE as procedure calls
+sql_call_statement
+    : CALL routine_name function_argument? ('.' id_expression function_argument?)* (INTO bind_variable)?
+    ;
+
+// PL/SQL block level: CALL keyword is OPTIONAL (standard PL/SQL allows direct procedure calls)
+// Support method chaining: obj_constructor(...).method(...) or CALL obj_constructor(...).method(...)
+plsql_call_statement
+    : CALL? routine_name function_argument? ('.' id_expression function_argument?)* (INTO bind_variable)?
     ;
 
 pipe_row_statement
@@ -5790,10 +5803,11 @@ set_constraint_command
 
 // https://docs.oracle.com/cd/E18283_01/server.112/e17118/statements_4010.htm#SQLRF01110
 // https://docs.oracle.com/en/database/oracle/oracle-database/21/sqlrf/COMMIT.html
+// BYT-8268: Fixed to allow WRITE clause independently, not just after COMMENT
+// Correct Oracle syntax: COMMIT [WORK] [COMMENT 'text'] [WRITE [WAIT|NOWAIT] [IMMEDIATE|BATCH]] [FORCE...]
 commit_statement
-    : COMMIT WORK?
-      ( COMMENT CHAR_STRING write_clause?
-      | FORCE ( CHAR_STRING (',' numeric)?
+    : COMMIT WORK? (COMMENT CHAR_STRING)? write_clause?
+      ( FORCE ( CHAR_STRING (',' numeric)?
               | CORRUPT_XID CHAR_STRING
               | CORRUPT_XID_ALL
               )
@@ -6952,8 +6966,9 @@ collection_name
     : identifier ('.' id_expression)?
     ;
 
+// BYT-8268: Database link names can include domain qualifiers (e.g., linkname.domain)
 link_name
-    : identifier
+    : identifier ('.' id_expression)*
     ;
 
 column_name