Fix duplicate step definitions and update version to 4.3.5

Changes:
- Removed duplicate step definitions in tuples_only.py that already exist
  in command_option.py to avoid AmbiguousStep errors
- Updated version from 4.3.4 to 4.3.5

All BDD tests passing: 7 scenarios, 32 steps ✓

Made with ❤️ and 🤖 Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

Author: DiegoDAF

pgcli/__init__.py

@@ -1 +1 @@
-__version__ = "4.3.4"
+__version__ = "4.3.5"

tests/features/steps/tuples_only.py

@@ -92,20 +92,3 @@ def step_see_multiple_data_rows(context):
 
     # Should not have table formatting
     assert "+-" not in output, f"Expected no table borders, but got: {output}"
-
-
-@then("we see the command output")
-def step_see_command_output(context):
-    """Verify that the special command output is present."""
-    output = context.cmd_output.decode('utf-8')
-    # For special commands like \dt, just verify it didn't error
-    assert context.exit_code == 0, f"Expected exit code 0, but got: {context.exit_code}"
-
-
-@then("pgcli exits successfully")
-def step_pgcli_exits_successfully(context):
-    """Verify that pgcli exited with code 0."""
-    assert context.exit_code == 0, f"Expected exit code 0, but got: {context.exit_code}. Output: {context.cmd_output.decode('utf-8')}"
-    # Clean up
-    context.cmd_output = None
-    context.exit_code = None