Efcore: Update external dependencies to latest GA releases

[ajcvickers]

• System.Threading.Tasks.Extensions (4.5.2)
  https://github.com/aspnet/EntityFrameworkCore/blob/release/3.0/src/EFCore/EFCore.csproj#L27

• Castle.Core (4.2.1)
  https://github.com/aspnet/EntityFrameworkCore/blob/release/3.0/src/EFCore.Proxies/EFCore.Proxies.csproj#L19

• Microsoft.Azure.Cosmos (3.0.0)
  https://github.com/aspnet/EntityFrameworkCore/blob/release/3.0/src/EFCore.Cosmos/EFCore.Cosmos.csproj#L25

• SQLitePCLRaw (2.0.1)

[ajcvickers]

/cc @AndriySvyryd for Cosmos
@bricelam Can you take a look at the other two?

(We don't necessarily have to update, but if there are newer RTM packages we might want to update.)

Thanks @JunTaoLuo for identifying these

[ajcvickers]

/cc @Pilchie FYI

[AndriySvyryd]

Cosmos is already at 3.0.0 https://github.com/aspnet/EntityFrameworkCore/blob/release/3.0/eng/Versions.props#L15

[ajcvickers]

@AndriySvyryd Right, but there is a 3.1.1 package now.

[AndriySvyryd]

I'm not sure we should upgrade unless we need to, users can always bump it up manually.

[ajcvickers]

@AndriySvyryd Can you try to find out what they fixed between 3.0 and 3.1.1? There might be critical issues that we should update for.

[bricelam]

System.Threading.Tasks.Extensions is for downlevel ValueTask. We can dump it.

[ajcvickers]

@bricelam Is it breaking to remove the reference in 3.1, or would it be a no-op anyway?

[bricelam]

The current package actually looks like it will break .NET Standard 2.1 projects. We should remove it in 3.0

[AndriySvyryd]

Here's the changelog: https://github.com/Azure/azure-cosmos-dotnet-v3/blob/releases/3.1.1/changelog.md
I think the only fix our users would benefit from is not using the current culture

[ajcvickers]

@AndriySvyryd Thanks. Given where we are, I agree we stay with 3.0 here. Test coverage is not as good as for other providers.
@bricelam Thanks. We should do an ask-mode PR for this.

[ajcvickers]

@bricelam Looks like our Castle.Core is quite old; given that it only impacts proxies and test coverage is pretty good I think we should update this for 3.0 as well. Thoughts?

[bricelam]

Agreed, fine to leave. Release notes:
https://github.com/castleproject/Core/releases/tag/v4.3.0
https://github.com/castleproject/Core/releases/tag/v4.3.1
https://github.com/castleproject/Core/releases/tag/v4.4.0

[ajcvickers]

@bricelam So you think we _should_ or _should not_ update our Castle reference?

[bricelam]

Oh, lol. Either way--it's low risk and low value. 😉

[ajcvickers]

@bricelam I read through the release notes in more detail. Let's leave as is for now, but we should update for 3.1 or at the latest 5.0the version after 3.1.

[bricelam]

Our analyzer depends on Microsoft.CodeAnalysis.CSharp.Workspaces. Is it safe to update this package? We really only need to work with the version of Roslyn that ships in VS2019 16.3 and the .NET Core 3.0 SDK, right? (3.3.0)

[bricelam]

Filed #17625