EnumValueOptions type ambiguity after upgrading to 2.5.0

[alex-zyl]

Description

Autogenarated code ends-up with reference conflicts after upgrading to Confluent.SchemaRegistry.Serdes.Protobuf 2.5.0 if EnumValueOptions is declared in proto file.

CS0433 The type 'EnumValueOptions' exists in both 'Google.Protobuf, Version=x, Culture=neutral, PublicKeyToken=x' and 'protobuf-net.Reflection, Version=x, Culture=neutral, PublicKeyToken=x

How to reproduce

Use Confluent.SchemaRegistry.Serdes.Protobuf 2.5.0

Add gRPC tools:

<PackageReference Include="Grpc.Tools" Version="2.65.0">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>

Add proto:

    <Protobuf Include="my.proto" />

syntax = "proto3";

package mds_schema.common.v1;

import "google/protobuf/descriptor.proto";

option java_package = "my.schema;
option java_multiple_files = true;


extend google.protobuf.EnumValueOptions {
  optional string enum_value_str = 300880;
}

Checklist

Please provide the following information:

• A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
• Confluent.Kafka nuget version.
• Apache Kafka version.
• Client configuration.
• Operating system.
• Provide logs (with "debug" : "..." as necessary in configuration).
• Provide broker log excerpts.
• Critical issue.