Provide ROPC warning on connections strings per SFI learn.microsoft.com mandate

[Rick-Anderson]

Issue or suggestion

This issue is a copy of dotnet/AspNetCore.Docs#33226

See the warning just above SQL Server Express LocalDB and follow see Secure authentication flows.

That's how we're handing potential ROPC risks. Ultimately customers will deploy apps to production. Most of the work is done in a few include files to choose from

dotnet_EntityFramework_Docs

• Connection Strings
• Connection strings and models
• Scaffolding (Reverse Engineering)
• Configuration File Settings
• EF Core tools reference (Package Manager Console) - EF Core
• EF Core tools reference (.NET CLI) - EF Core
• Multi-tenancy - EF Core
• Azure Cosmos DB Provider - EF Core
• What's New in EF Core 5.0
• Entity Framework 6 SQL Server provider based on Microsoft.Data.SqlClient
• Visual Studio Releases - EF6
• Applying Migrations - EF Core
• Port from EF6 to EF Core - Detailed Cases
• Using migrate.exe - EF6
• Database Providers - EF Core
• Porting from EF6 to EF Core - Porting a Code-Based Model - EF
• Tools & Extensions - EF Core
• DbContext Lifetime, Configuration, and Initialization - EF Core
• Enum Support - EF Designer - EF6
• Code First Conventions - EF6
• Interceptors - EF Core
• Database First - EF6
• What's New in EF Core 6.0
• Code First to an Existing Database - EF6
• Advanced Performance Topics
• Entity Framework Designer Keyboard Shortcuts - EF6
• Breaking changes in EF Core 7.0 (EF7) - EF Core
• Databinding with WinForms - EF6
• Databinding with WPF - EF6
• The Entity Framework 6 provider model - EF6
• Overview of Entity Framework Core - EF Core
• Upgrading from previous versions to EF Core 2 - EF Core
• Get Started with Windows Forms - EF Core
• Dependency resolution - EF6
• Porting from EF6 to EF Core - Behavior changes
• Porting from EF6 to EF Core - Porting an EDMX-Based Model - EF

CS effort for repos:
dotnet_EntityFramework_Docs

For details see:
SFI info in Teams

[Rick-Anderson]

@roji @ajcvickers @AndriySvyryd please review

[AndriySvyryd]

For EF6 pages consider putting a link to Entity Framework 6 SQL Server provider based on Microsoft.Data.SqlClient in the warning as using it is required to be able to follow the guidance.

I don't think that the warning is relevant on these pages:

• What's New in EF Core 5.0
• What's New in EF Core 6.0
• Breaking changes in EF Core 7.0 (EF7) - EF Core
• Upgrading from previous versions to EF Core 2 - EF Core
• Porting from EF6 to EF Core - Behavior changes
• Porting from EF6 to EF Core - Porting a Code-Based Model - EF
• Porting from EF6 to EF Core - Porting an EDMX-Based Model - EF
• Database Providers - EF Core
• Tools & Extensions - EF Core
• Applying Migrations - EF Core
• DbContext Lifetime, Configuration, and Initialization - EF Core
• Interceptors - EF Core
• Advanced Performance Topics

[AndriySvyryd]

Related:

• Incorrect connection string format in "DbContext in dependency injection for ASP.NET Core" #3071
• Fix sample code for connection strings from Configuration #3877
• Show more examples of obtaining and setting connection strings #1083
• Document changing connection/connection string #2075
• Document when PersistSecurityInfo=True is needed #2926
• Example for lazy initialization of connectionstring does not work when using password in connectionstring #4101