Reservation prefix check

[cursor]

Fix applyReservation to correctly identify SET @@RESERVATION statements, preventing incorrect skipping of DSN reservations due to overly broad prefix matching.

---

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[cursor]

PR Summary

Low Risk
Small, localized string-matching change that only affects when reservation statements are auto-injected into queries.

Overview
Tightens applyReservation’s detection of existing SET @@RESERVATION statements so the driver only skips injecting the DSN reservation when the query explicitly sets reservation via SET @@RESERVATION= or SET @@RESERVATION , rather than any broader prefix match.

^{Written by Cursor Bugbot for commit a8b2eff. Configure here.}