Missing argument on Visual Studio Example

I personally think there's an issue in the Using One Context Type section's examples.

In the .NET Core CLI Example, the project is specified as an parameter. In the Visual Studio package manager example, no project argument is supplied.

In my experience, if you don't specify the project as an argument, the target assembly does not match the migration assembly and generating migrations will fail.

The visual studio example requires the user to set the target project in Package Manager Console to match the migration's assembly but this isn't mentioned anywhere either. This can and in my opinion, should be avoided with the parameter like the .NET Core CLI example.

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 7b011c7a-3534-78e3-b491-addd96fb5ba1
* Version Independent ID: 371826c5-3ef2-4eef-32e9-d55c777cd9d3
* Content: [Migrations with Multiple Providers - EF Core](https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/providers?tabs=dotnet-core-cli)
* Content Source: [entity-framework/core/managing-schemas/migrations/providers.md](https://github.com/dotnet/EntityFramework.Docs/blob/main/entity-framework/core/managing-schemas/migrations/providers.md)
* Product: **entity-framework**
* Technology: **entity-framework-core**
* GitHub Login: @bricelam
* Microsoft Alias: **avickers**