Generated object builders don't guard against method name conflicts

Consider the following object definition:

types:
  definitions:
    objects:
      ConflictedObject:
        foo: list<string>
        addAllFoo: list<string>

The generated Java implementation fails to compile, as the builder ends up with the following pair of methods:

        public Builder addAllFoo(Iterable<String> foo) {
            ConjureCollections.addAll(this.foo, Objects.requireNonNull(foo, "foo cannot be null"));
            return this;
        }

        @JsonSetter("addAllFoo")
        public Builder addAllFoo(Iterable<String> addAllFoo) {
            this.addAllFoo.clear();
            ConjureCollections.addAll(
                    this.addAllFoo, Objects.requireNonNull(addAllFoo, "addAllFoo cannot be null"));
            return this;
        }

It seems like the first method's name should be munged in some way to avoid the conflict, like addAllFoo_.

No source file or test is named. Reproduce the ConflictedObject YAML example and inspect the generated Java builder methods; done means the generated implementation compiles without a method-name collision while retaining both object-field behaviors.