fix: stale query bindings, MSSQL MAX size, and Column attribute name

[usernane]

Summary

Merge dev into main with three bug fixes and observability improvements.

Motivation

• MSSQL error 245 (varchar to int conversion) when migrations fail before execute()
• varbinary(max) / varchar(max) columns created as size 1 on MSSQL
• #[Column(name: 'created_at')] attribute name parameter ignored for property-level columns

Changes

• fix: reset stale query bindings — reset bindings in SchemaRunner catch blocks and SchemaChangeRepository::count(); add resetBinding() to update() in MySQL/MSSQL queries
• feat: Observability over Errors — improved exception visibility in schema runner
• fix: MSSQL MAX size (bug(MSSQLColumn): varbinary/varchar MAX size (-1) creates column with size 1 instead of MAX #163) — accept -1 in setSize() for MAX-capable types, output max in SQL
• fix: Column attribute name (bug: Column attribute 'name' parameter is ignored during table creation #159) — use explicit name from #[Column] attribute for property-level columns
• Closed AttributeTableBuilder does not create UNIQUE constraints for MSSQL columns #153 — UNIQUE constraints verified working, not reproducible

How to Test / Verify

composer test

Full suite: 882 tests, 2535 assertions, all passing.

Breaking Changes and Migration Steps

None

Checklist

• I reviewed my own diff before requesting review
• My commits follow Conventional Commits
• The title of the pull request follows Conventional Commits
• I added/updated tests (or explained why not)
• I updated docs (if needed)
• I ran lint/cs-fixer (if applicable)
• I considered backward compatibility
• I considered security

Related issues

Closes #163
Closes #159

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud