Unusable in modular Java projects

Since no module-info exists, nor does an Automatic-Module-Name exist in the MANIFEST.MF, the generated name of this library becomes "ergo.appkit.2.12" which is an invalid name because no part of it can start with a number.

Unfortunately, fixing that will not be enough because the dependencies of this library also do not come with a module name and result in invalid names being generated due to the strange library_2.12 format used by Scala.

However, that does not mean that appkit should not have an Automatic-Module-Name. For example, the scala standard library comes with one (scala.library).

The first step to rectifying this problem is to add an Automatic-Module-Name to appkit. It should be named `org.ergoplatform.appkit` in my opinion.

Inspect the build configuration that produces the library's MANIFEST.MF and compare it with the existing module metadata, noting that no module-info or Automatic-Module-Name is currently present. Add the requested org.ergoplatform.appkit name and verify the packaged artifact exposes it without changing the dependency issue described.

Written by the indexing model from the issue text.