Add .NET10 Support [API-2335][HZ-5252]

[emreyigit]

Upgraded libraries and added support for .NET10.

*The PublicAPI/net10.0 folder is direct copy of PublicAPI/net9.0. No review required.

Breaking Change on Hazelcast.Net.Linq.Async in NET10

Hazelcast.Linq package doesn't target to build for net10.0 since dotnet team moved some implementations from System.Linq.Async (in dotnet/reactive repo) to dotnet/runtime repo. dotnet/docs#44886 That also effects our LINQ package since we cannot depend on System.Linq.Async in dotnet/reactive in NET10 due to ambiguity.

So, if you like to use Hazelcast.Net.Linq.Async package on NET10, you should put alias resources coming over NET10 to resolve ambiguity between net10 and System.Linq.Async Version=6.0.0

In your csproj;

  <!-- START - This section is required to resolve reference ambigutity raised in NET10
  https://github.com/dotnet/docs/issues/44886
  -->
  <ItemGroup Condition="'$(TargetFramework)' != 'net10.0' and '$(TargetFramework)' != 'net462' and '$(TargetFramework)' != 'net48'">
    <PackageReference Include="System.Linq.AsyncEnumerable" Version="10.0.0" Aliases="SystemLinqAsyncEnumerable" />
  </ItemGroup>

  <Target Name="_SetAliasOnBuiltInSystemLinqAsyncEnumerable" BeforeTargets="ResolveAssemblyReferences">
    <ItemGroup Condition="'$(TargetFramework)' == 'net10.0'">
      <Reference Condition="'%(Reference.AssemblyName)' == 'System.Linq.AsyncEnumerable'">
        <Aliases>SystemLinqAsyncEnumerable</Aliases>
      </Reference>
    </ItemGroup>
  </Target>
  <!-- END - This section is required to resolve refence ambigutity raised in NET10 -->

Hopefully, after this transition is completed for LINQ related resources in dotnet, this fix will be unnecessary.