Give toolbar tests the sqlexecute property

[rolandwalker]

Description

Now that the prompt string can have data fetched from the connection, and now that the toolbar can have custom format strings, there are assertions in get_prompt() that we should satisfy in toolbar tests, by setting the sqlexecute property.

It's not clear how this has been passing up until now in CI.

Checklist

• I added this contribution to the changelog.md file.
• I added my name to the AUTHORS file (or it's already there).
• To lint and format the code, I ran

  uv run ruff check && uv run ruff format && uv run mypy --install-types .
  

[github-actions]

Findings:

1. Medium: these tests were converted from unit tests into integration tests, so they now get skipped when no DB is available (@dbtest), which removes toolbar coverage in many environments and can hide regressions in non-DB toolbar behavior.

   • Location: test/test_clitoolbar.py:11, test/test_clitoolbar.py:38
   • Action: replace real SQLExecute(...) with a lightweight stub/fake sqlexecute object that satisfies get_prompt() assertions (server_info.species, etc.) without requiring a live connection.

2. Low: each test opens a real DB connection via SQLExecute(...) and never closes it. This can leak connections in longer test runs.

   • Location: test/test_clitoolbar.py:14, test/test_clitoolbar.py:41
   • Action: close in teardown (m.sqlexecute.close()) or use a fixture with yield cleanup.

Security concerns:

• No new security issues identified in this PR’s diff.

Validation note:

• I could not execute tests in this environment because pytest/uv are not installed.