Fix SQL extraction test expected values after rstrip(';') change.

The rstrip(';') applied to each block before joining means single
blocks and the last block in multi-block joins no longer have
trailing semicolons. Update expected values to match.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: dpage

web/pgadmin/tools/sqleditor/tests/test_nlq_chat.py

@@ -214,7 +214,7 @@ class NLQSqlExtractionTestCase(BaseTestGenerator):
                 '```sql\nSELECT * FROM users;\n```\n\n'
                 'This returns all users.'
             ),
-            expected_sql='SELECT * FROM users;'
+            expected_sql='SELECT * FROM users'
         )),
         ('SQL Extraction - Multiple SQL blocks', dict(
             response_text=(
@@ -227,11 +227,11 @@ class NLQSqlExtractionTestCase(BaseTestGenerator):
         )),
         ('SQL Extraction - pgsql language tag', dict(
             response_text='```pgsql\nSELECT 1;\n```',
-            expected_sql='SELECT 1;'
+            expected_sql='SELECT 1'
         )),
         ('SQL Extraction - postgresql language tag', dict(
             response_text='```postgresql\nSELECT 1;\n```',
-            expected_sql='SELECT 1;'
+            expected_sql='SELECT 1'
         )),
         ('SQL Extraction - No SQL blocks', dict(
             response_text=(
@@ -264,7 +264,7 @@ class NLQSqlExtractionTestCase(BaseTestGenerator):
                 'SELECT u.name, o.total\n'
                 'FROM users u\n'
                 'JOIN orders o ON u.id = o.user_id\n'
-                'WHERE o.total > 100;'
+                'WHERE o.total > 100'
             )
         )),
     ]