Add print_database_tables()

[Meghansaha]

Summary

This PR addresses #285 by adding:

• print_database_tables()
• _handle_connection_errors()
• updates to connect_to_table()

The new _handle_connection_errors() function pulls out the connection checks that were previously built into connect_to_table() and makes them reusable. It’s also been expanded to handle database-level checks, not just tables. Both print_database_tables() and connect_to_table() now rely on it for consistent error handling.

Test Coverage

Added full test coverage for all new and updated connection utilities:

• connect_to_table() — 1 test updated, plus 5 new tests for success cases, missing dependencies, invalid tables, and error handling
• print_database_tables() — 6 new tests covering table listing, dependency checks, and memtable filtering
• _handle_connection_errors() — covered indirectly through connection error scenarios in the tests above

---

Related GitHub Issues and PRs

• Ref: add method to print/iterate through available duckdb/sqlite tables #285

Checklist

• I understand and agree to the Code of Conduct.
• I have followed the Style Guide for Python Code as best as possible for the submitted code.
• I have added pytest unit tests for any new functionality.

[Meghansaha]

@rich-iannone Tried to make this as complete as possible! Getting full test coverage took some work (with a little help from Copilot 😅), but I’m showing 100% coverage locally for the changes in this PR. I did try to pull in the .github workflow ci/test yml from main to see if the 3.14 build check would magically pass for me, but it did not lol. Let me know if you’d like to discuss anything further.