Dotnet client not throwing when duplicate stream id is created with StreamState.NoStream

[awillsoft]

Description
Dotnet GRPC client AppendToStreamAsync method is not throwing exception error when duplicated streams ids are created with same stream name and expected state is StreamState.NoStream,
instead of throwing, they are returning same log position number of already created stream.

this is not the expected behavior like is expected and documentation says:

When appending events to a stream, you can supply a stream state or stream revision. Your client uses this to inform EventStoreDB of the state or version you expect the stream to be in when appending an event. If the stream isn't in that state, an exception will be thrown.

Handling concurrency

To Reproduce
Steps to reproduce the behavior:

        var streamStateNoStrem = StreamState.NoStream;

        var cd = await client.AppendToStreamAsync(streamName, streamStateNoStrem, events, cancellationToken: cancellationToken);
        var cd2 = await client.AppendToStreamAsync(streamName, streamStateNoStrem, events, cancellationToken: cancellationToken);

[linear]

DB-1932

[alexeyzimarev]

It is literally that code? Because if events content is the same, the server will treat it as idempotent append (appending the same records using the same expected version) and it won't throw.