Kotlin generated builder rename method if name conflicts with proto types.

For instance

optional int32 int32 = 1;

in Java, the builder will be

    public Builder int32(Integer int32) {
      this.int32 = int32;
      return this;
    }

in Kotlin, the builder will be (it includes the package in the name)

    fun squareup_proto3_kotlin_alltypes_int32(squareup_proto3_kotlin_alltypes_int32: Int): Builder {
      this.squareup_proto3_kotlin_alltypes_int32 = squareup_proto3_kotlin_alltypes_int32
      return this
    }

Maybe it was by design to keep the builder's setter samely named as the property?

Start by locating the Kotlin builder-generation entry point for protobuf fields and reproduce the generated output for a field named int32. Compare the Kotlin and Java naming behavior shown in the issue, then determine whether the package-qualified setter is intentional. Done means the naming conflict has a documented or corrected resolution, with generation coverage for this case.