bug: compatibleWith does not work when declaring multiple packages with both target versions and no target versions

[LisoUseInAIKyrios]

Bug description

compatibleWith("app1", "app2"("1.2.3"))

Does not work, and is a compile error.
The compatibleWith method has two overloads of varargs, one with varargs of no version restrain and another with varargs with a version restrain. So mixing the two fails to compile since they're different types.
 

compatibleWith("app1"(), "app2"("1.2.3"))

Does compile, but app1 is always rejected as incompatible no matter what version app is patched.

Acknowledgements

• I have checked all open and closed bug reports and this is not a duplicate.
• I have chosen an appropriate title.
• All requested information has been provided properly.

[oSumAtrIX]

Second behavior is correct. Empty list = compatible with no version (can be used to define explicit incompatibility)

[LisoUseInAIKyrios]

Will that explicit incompatibility be shown correctly? I would guess the website and/or Manager would display it is compatible (or at least suggest it is compatible).

I think modifying patcher to treat app() the same as app could be a solution to this unusual use case. Logically it makes sense since both app and app() don't define any version, and patches don't normally explicitly define what's not compatible (they only declare what is compatible).

[oSumAtrIX]

Null is distinct from empty. Null means any, empty means none. I am not sure how manager handles it, but cli should handle it correctly. There's suggestions regarding the API to be changed to:

compatibleWith(
"App" { name, code -> name == "" }
)

However this makes it impossible to serialize compatible versions to string to display to the user and verbose code