fix: update foreign key handling to use 'reference'

[AxiosLeo]

instead of 'reference' for consistency and compatibility

---

Note

Low Risk
Mostly a naming/compatibility change in SQL generation for foreign keys; risk is limited to callers that still pass reference and could hit validation/undefined access if not covered.

Overview
Foreign key definitions are standardized to use references instead of reference in ManageSQLBuilder.

createForeignKey and table createColumns now validate/render from options.references and normalize onDelete/onUpdate (defaulting to NO ACTION), while createColumns and migration.createForeignKey accept the legacy reference field by mapping it to references. Tests were updated to use references and a new test was added to ensure legacy reference still works.

^{Written by Cursor Bugbot for commit ac909d1. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}