Resolve yang-parser-api naming

We have yang-parser-api, which exposes the same module (automatic) and really has yang.model.parser.api inside. We should be renaming the artifact or the package to make room for it, but it is kinda sticky.

OTOH, we can jump into the business of having multiple API packages in one JPMS module – that would probably work, too.