Improve change tracking and update performance

[roji]

This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.

---

Update pipeline perf work done in 7.0 is summarized in #26797.

Backlog

• Allow managing transactions via SQL commands in the update pipeline #27532
• Determine how to look up join entity types at model building time #21901
• Perf: Attaching a graph is slow #10618
• Generate bespoke Attach and DetectChanges as part of the compiled model #32088
• Implement bulk deletion #27550
• Use the new batching API from ADO.NET #18990
• Do not track after SaveChanges() #9118
• Perf: Reuse command batches in update pipeline #11574
• Recycle ADO.NET objects in update pipeline #15546
• Allow opt-out of optimistic concurrency/rows affected check in the model #10443
• Stop generated cascade delete statements when the DeleteBehavior is database-side #21521
• Create an alternate key for join entity types which have an independent PK #21900
• Strategy for inserting rows with table-values parameters #2484