nbm-maven-plugin A few error messages improvements

I think for a beginner these error messages are absolute hell, but even for me, an experienced one, it's quite a time killer. For the friend dependency I need to find the correct group and artifactId. For the transitive module I can define module as direct dependency directly from NB, but when I have 150 modules in there, that search also takes a while. And yet the plugin has this information directly in itself, it just needs to be used...
Alternatively, a parameter could be added to the configuration to disable them. But for me they should be on by default..

```
Failed to execute goal org.apache.netbeans.utilities:nbm-maven-plugin:14.3-SNAPSHOT:manifest (default-manifest) on project ZapliScadaEditor:
Module has friend dependency on org.netbeans.modules.java.hints but is not listed as a friend.
```

vs

```
Failed to execute goal org.apache.netbeans.utilities:nbm-maven-plugin:14.3-SNAPSHOT:manifest (default-manifest) on project ZapliScadaEditor:
Module has friend dependency on org.netbeans.modules.java.hints but is not listed as a friend.
Add the following lines to the plugin configuration:

...

org.netbeans.modules:org-netbeans-modules-java-hints
impl

...

```

```
Project uses classes from transitive module org.netbeans.api:org-openide-io:jar:RELEASE126-ZAPLI1 which will not be accessible at runtime.
To fix the problem, add this module as direct dependency. For OSGi bundles that are supposed to be wrapped in NetBeans modules, use the useOSGiDependencies=false parameter
```

vs

```
Project uses classes from transitive module org.netbeans.api:org-openide-io:jar:RELEASE126-ZAPLI1 which will not be accessible at runtime.
To fix the problem, add this module as direct dependency. For OSGi bundles that are supposed to be wrapped in NetBeans modules, use the useOSGiDependencies=false parameter
Add the following lines to the dependencies:

org.netbeans.api
org-openide-io
${netbeans.version}

```

No source file or test is named in the issue. Start at the nbm-maven-plugin manifest goal and trace where the friend-dependency and transitive-module error messages are produced; check the existing plugin tests if available. Done means both messages include usable dependency configuration snippets like the examples, while retaining the explanatory guidance.

Written by the indexing model from the issue text.