Ambiguous method overloading for method qupath.lib.regions.RegionRequest#createInstance.

Ambiguous method overloading in the context of `qupath.lib.regions.RegionRequest` refers to a situation where there are multiple methods with the same name, `createInstance()`, in the `RegionRequest` class or its subclasses within the `qupath.lib.regions` package. This ambiguity can occur when two or more methods have different parameter lists, types, or both, but they all share the same method signature.

For example:

public class RegionRequest {
    public static RegionRequest createInstance(String type) {
        // Method implementation for one version
    }

    public static RegionRequest createInstance(int x, int y, int width, int height) {
        // Method implementation for another version
    }
}

Here, both `createInstance(String)` and `createInstance(int, int, int, int)` are considered overloads since their names are identical but they accept different arguments. In order to resolve this ambiguity, the Java compiler requires either additional information like method hints, explicit casting, or using an annotation to indicate which method should be called based on the provided parameters.

If you encounter this issue while using the library, it is important to consult the API documentation or the library's source code to determine the correct usage syntax, as the exact solution will depend on the intended behavior and how the developers defined these methods.