Bump Microsoft.EntityFrameworkCore.Design from 7.0.0 to 7.0.3

[dependabot[bot]]

Bumps Microsoft.EntityFrameworkCore.Design from 7.0.0 to 7.0.3.

Release notes

Sourced from Microsoft.EntityFrameworkCore.Design's releases.

EF Core 7.0.3

This is a patch release of EF Core 7.0 containing only important bug fixes:

• Add-Migration fails with "An item with the same key has already been added" when renaming entity
• ExecuteUpdate fails when target entity has an owned entity
• EF Core 7 Rev eng: Missing HasForeignKey when referencing a navigation property with a unique constraint with DataAnnotations on
• Change in behaviour of CSharpHelper.Identifier(string name)
• NullReferenceException scaffolding when no primary key set
• Idempotent migration script not working on EFCore7.0 for AlterColumn when nullable changed from true to false
• 6.0.11 to 7.0.0: [...] are both mapped to column [..] but are configured to use differing provider types ('double' and 'double?').'
• Generated Model Snapshot throws InvalidOperationException
• SQL Server bulk insert broken when new command applies pending commands and goes over the batch parameter limit
• Invalid singularization when scaffolding a manytomany table
• In EF7, SqLite unable to load spatialite using the NetTopologySuite Package
• Cannot access property through interface in ExecuteUpdate setter lambda
• DbContext scaffold missing IndexerProperty for M2M relation after moving to EF Core 7
• Performance regression in model building in Entity Framework Core 7
• Mixing sproc and non-sproc commands in the same batch may fail with a NullReferenceException
• Condition's order will cause different result when using .Contains() to search string cross varchar and nvarchar columns
• SaveChanges circular dependency in unique unfiltered index
• QueryTrackingBehavior resets to TrackAll when using DbContext pooling
• EFCore 7.0.0 - Graph of entity insertion throws a FK exception
• Replacing PK to PK TPH dependent with different type fails
• dotnet ef migrations add freezes
• InvalidOperationException when mapping properties of different types to the same column
• Obsoletion message for AutoTransactionsEnabled is wrong
• Incorrect NullReferenceException for parameter in split query with GroupBy

EF Core 7.0.2 (EF7)

This is a patch release of EF Core 7.0 containing only important bug fixes:

• Exception when inserting multiple rows into the same table on SQL Server

EF Core 7.0.1 (EF7)

This is a patch release of EF Core 7.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 7.0.1.

Commits

• 01a74cc Merge in 'release/7.0' changes
• 00e218a [release/7.0] Take schema into account when comparing FK constraints. (#30047)
• 32bfe8b Merge in 'release/7.0' changes
• 9cbf778 Merge branch 'release/6.0' into release/7.0
• c5072f2 Merge in 'release/7.0' changes
• 02e112a Merge branch 'release/3.1' into release/6.0
• 10f1d39 [release/7.0] Correct [Obsolete] message for AutoTransactionBehavior (#30040)
• 21c33ba [release/7.0] Update to SQLitePCLRaw 2.1.4 (#30036)
• 895be6c [release/7.0] Fix split query over GroupBy over parameter (#30024) (#30030)
• c672347 Merge pull request #30019 from vseanreesermsft/internal-merge-3.1-2023-01-10-...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)