Update EF Core tooling breaking change

[guardrex]

Addresses #34775

Let's see if this looks better. I think with a minor update to this approach at 10.0 to remove the remark about .NET 10's release (and to update the link so that it just points to the downloads page at https://dotnet.microsoft.com/download), this is a better way to handle a tooling breaking change that will be patched for 10.0. Maybe! 🤔 ... best to sleep on it for sure 🛌💤.

cc: @Rick-Anderson @tdykstra ... Discussed further with Wade offline. I'm looking at a different approach here for this because this really is a temporary tooling (SDK) problem.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/tutorials/movie-database-app/part-2.md	aspnetcore/blazor/tutorials/movie-database-app/part-2

[guardrex]

Yeah ... I do think I like this approach better.

I'll just need to swing back into this at 10.0 GA to update that first bullet to just say to use a .NET 10 or later SDK and cross-link to the main downloads page.

That will harden this up for the future (.NET 10 or later), and it has the nice side benefit of less text to maintain.

[guardrex]

@wadepickett @Rick-Anderson @tdykstra (... get well Tom! 🤕)

They just told me that they're reverting what they did that causes the breaking change. This whole problem will go away when the 9.0.300 SDK comes out.

I'll revise this to that effect.

[guardrex]

OK! That licks IT! 🐮👅

I'll remove this when 9.0.300 lands.