[release/9.0] Don't suppress transactions when creating the history repository

[AndriySvyryd]

Fixes #35127
Addresses dotnet/docs-aspire#2151

Description

When applying migrations the first time to a database EF creates a history table to keep track of the applied migrations.

In EF 9.0 this action was made idempotent to mitigate issues from concurrent applications as for some providers this is done before acquiring an exclusive migrations lock.

However, it was erroneously suppressing transactions.

Customer impact

When calling Migrate in an explicit transaction an exception is thrown. This is common in Aspire scenarios. The workaround is to remove the explicit transaction.

How found

Multiple customer reports on 9 (5 so far).

Regression

Yes, from 8.

Testing

Tests added.

Risk

Low.