✨ Making factory functions of companion objects static on Java

[LVMVRQUXL]

📝 Description

Like suggested by @lbunschoten in #335 (comment), we want to mark the factory functions of companion objects with the JvmStatic annotation for making them statically available on Java.

Here are examples of calling the NotBlankString.create(Any?) function from Java code:

val value = "Kotools Types is awesome!"

// Actual
NotBlankString.Companion.create(value); // passes
NotBlankString.create(value); // compilation error

// Expected
NotBlankString.Companion.create(value); // passes
NotBlankString.create(value); // passes

✅ Checklist

• Mark the NotBlankString.Companion.create(Any?) function, test its new API for Java and dump the Application Binary Interface (ABI).
• Mark the NotBlankString.Companion.createOrNull(Any?) function, test its new API for Java and dump the ABI.
• Mark the NonZeroInt.Companion.create(Number) function, test its new API for Java and dump the ABI.
• Mark the NonZeroInt.Companion.createOrNull(Number) function, test its new API for Java and dump the ABI.
• Mark the PositiveInt.Companion.create(Number) function, test its new API for Java and dump the ABI.
• Mark the PositiveInt.Companion.createOrNull(Number) function, test its new API for Java and dump the ABI.
• Mark the NegativeInt.Companion.create(Number) function, test its new API for Java and dump the ABI.
• Mark the NegativeInt.Companion.createOrNull(Number) function, test its new API for Java and dump the ABI.
• Mark the StrictlyPositiveInt.Companion.create(Number) function, test its new API for Java and dump the ABI.
• Mark the StrictlyPositiveInt.Companion.createOrNull(Number) function, test its new API for Java and dump the ABI.
• Mark the StrictlyNegativeInt.Companion.create(Number) function, test its new API for Java and dump the ABI.
• Mark the StrictlyNegativeInt.Companion.createOrNull(Number) function, test its new API for Java and dump the ABI.
• Mark the StrictlyPositiveDouble.Companion.create(Number) function, test its new API for Java and dump the ABI.
• Mark the StrictlyPositiveDouble.Companion.createOrNull(Number) function, test its new API for Java and dump the ABI.
• Mark the StrictlyNegativeDouble.Companion.create(Number) function, test its new API for Java and dump the ABI.
• Mark the StrictlyNegativeDouble.Companion.createOrNull(Number) function, test its new API for Java and dump the ABI.
• Mark the NotEmptyList.Companion.create(Collection) function, test its new API for Java and dump the ABI.
• Mark the NotEmptyList.Companion.createOrNull(Collection) function, test its new API for Java and dump the ABI.
• Mark the NotEmptyList.Companion.of(E, vararg E) function, test its new API for Java and dump the ABI.
• Mark the NotEmptySet.Companion.create(Collection) function, test its new API for Java and dump the ABI.
• Mark the NotEmptySet.Companion.createOrNull(Collection) function, test its new API for Java and dump the ABI.
• Mark the NotEmptySet.Companion.of(E, vararg E) function, test its new API for Java and dump the ABI.
• Mark the NotEmptyMap.Companion.create(Map) function, test its new API for Java and dump the ABI.
• Mark the NotEmptyMap.Companion.createOrNull(Map) function, test its new API for Java and dump the ABI.
• Mark the NotEmptyMap.Companion.of(Pair, vararg Pair) function, test its new API for Java and dump the ABI.
• Add an entry for this issue in the unreleased changelog.

[LVMVRQUXL]

The factory functions of the EmailAddress type will be deprecated by #623.