Add multi-column foreign key support to fluent syntax

[Copilot]

• [x] Add multi-column foreign key support to fluent syntax for SQLite
• [x] Create comprehensive tests and documentation
• [x] Fix parameter order in method signatures (foreignColumns should come before primaryTableSchema)
• [x] Update collection initializers to use modern C# syntax []
• [x] Update interface definitions to match corrected parameter order
• [x] Update implementation classes to match corrected parameter order
• [x] Update documentation to reflect correct method signatures
• [x] Update examples to use modern collection initializer syntax
• [x] Rebase with main to get latest fixes
• [x] Move test from SQLite-specific class to BaseTableTests as abstract method per feedback
• [x] Implement abstract method for all generator test classes to ensure compilation
• [x] Fix SQL Server test to include foreign key creation statement verification
• [x] Trigger GitHub Actions workflow for validation

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions[bot]]

Test Results

0 tests   0 ✅  0s ⏱️ 0 suites  0 💤 0 files    0 ❌

Results for commit dc274932.

[github-actions[bot]]

Test Results

    1 files      1 suites   33s ⏱️ 5 327 tests 4 995 ✅ 332 💤 0 ❌ 5 808 runs  5 212 ✅ 596 💤 0 ❌

Results for commit 07686773.

:recycle: This comment has been updated with latest results.

[jzabroski]

@copilot rebase with main to get latest fixes

[Copilot]

@copilot rebase with main to get latest fixes

Completed rebase with main branch. The branch has been successfully rebased with the latest fixes from main branch commit f9bf479f.

[jzabroski]

@copilot Recreate this PR as a new PR

[Copilot]

@copilot Recreate this PR as a new PR

I understand you want me to recreate this PR as a new PR. However, I don't have the ability to create new PRs or push to new branches directly. Could you clarify what you'd like me to do?

Options I can consider:

1. Reset the current branch and start fresh with the changes
2. Create a different branch name locally and you can create the new PR from that
3. Something else specific you have in mind

What would work best for your workflow?

[jzabroski]

@copilot Update this PR to help trigger a new GitHub Action workflow for this PR so that we can validate all the tests pass.

[Copilot]

@copilot Update this PR to help trigger a new GitHub Action workflow for this PR so that we can validate all the tests pass.

Updated PR to trigger GitHub Actions workflow in commit 0768677.