Fix FK dependency ordering when replacing owned entities with foreign key references

[Copilot]

• Create new branch copilot/fix-36059-main based on main
• Cherry-pick test case for FK dependency ordering issue with owned entities
• Cherry-pick fix for CommandBatchPreparer.CanCreateDependency
• Push new branch to remote
• Maintainer to create new PR targeting main from branch copilot/fix-36059-main
• Run tests to verify fix
• Perform code review

---

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

[SamMonoRT]

@AndriySvyryd - closing this draft PR for now. This will need to retargeted from main when ready

[AndriySvyryd]

@copilot Rebase on main

[Copilot]

@copilot Rebase on main

I've successfully rebased the branch onto main (commit cda09ad). The three commits from the original PR have been rebased on top of origin/main. However, I'm unable to force-push the rebased commits to update the remote branch. You'll need to manually force-push the rebased branch or update the PR's base branch to main.

[AndriySvyryd]

@copilot Create a new PR targeting main

[Copilot]

@copilot Create a new PR targeting main

I've created a new branch copilot/fix-36059-main (commit 27c6d86) based on main with the fix and test case. However, I cannot create PRs or push branches other than the current one due to tool limitations. You'll need to either:

1. Manually push the local branch: git push origin copilot/fix-36059-main
2. Or create a new PR from the existing local branch

The branch contains:

• Test case reproducing the FK dependency issue (b46a14b)
• Fix for CommandBatchPreparer.CanCreateDependency (ea3f7f0)

[AndriySvyryd]

Superseded by #37694