[maven-release-plugin] prepare release maven-3.1.1
[maven-release-plugin] prepare for next development iteration
change scm view url to GitHub mirror: automatic url of modules does not
work with Apache's GitWeb but is ok with GitHub
[MNG-5513] Artifact filtering for Eclipse Aether fixed

The filtering was left unchanged, while Aether
GroupID changed from org.sonatype.aether to
org.eclipse.aether, basically letting
Plugins to reference Eclipse Aether that
would produce runtime Linkage errors.
[MNG-5513] Restoring Maven 3.0.x style behavior

As it was importing org.sonatype.aether.impl and
sub packages, but since Aether move to Eclipse
the org.eclipse.aether.internal.impl is no longer
sub package of org.eclipse.aether.impl (but it
was in Sonatype Aether)
Add a LICENSE/NOTICE that can be picked up for the src assembly
use project.scm.tag property in web access to avoid value change when
releasing or branching
fix scm connection and developerConnection values in modules, waiting
for maven-scm support of default inherited values, which appends
/${artifactId}
fix scm connection and developerConnection values in modules, waiting
for maven-scm support of default inherited values, which appends
/${artifactId}
Change poms over to major.minor-SNAPSHOT
Merge branch 'mng-5513'
We must also filter out the old Aether as well to prevent NoClassDefFoundErrors
MNG-5513: Artifact filtering not updated for Eclipse Aether filtering

Also, please note that org.eclipse.aether.internal.impl should be imported into plugin realms, thereby restoring Maven 3.0.x style behavior which imports org.sonatype.aether.impl and sub packages (especially o.s.a.impl.internal which after the move to Eclipse is no longer a sub package of o.e.a.impl)  according to Benjamin (thanks!)
I'm reverting this as per Benjamin: the change to the artifact filter is an optimization to avoid downloading needless artifacts, but for cases of uber JARs or other stuff pulling in those packages, the class realm manager's imports are crucial
[maven-release-plugin] prepare release maven-3.1.1
[maven-release-plugin] prepare for next development iteration
The version:set plugin works to roll/unroll changes (where the release plugin is not very good) so we can use more standard versions which will help withe ITs.
Adding envar MAVEN_CMD_LINE_ARGS to shell scripts to provide consistency for accessing CLI args via env.MAVEN_CMD_LINE_ARGS user property (from plugins, for example).
MNG-5530 Introduced mojo execution guice component scope

Mojo execution scoped components are annotated with @MojoExecutionScoped
They are created just before configured mojo instance is created
and disposed immediately after mojo execution finishes.

Execution scoped components can request @Inject MavenSession,
MavenProject and MojoExecution instances in addition to any
standard Maven core components and components defined in
maven plugin contributing execution scoped components.

Execution scoped components can be injected into Mojos using
standard /* @component */ javadoc (and likely new mojo
annotations).

If execution scoped component implements MojoExecutionListener
callback interface, its #afterMojoExecutionSuccess method will be
invoked after successful mojo execution and #afterMojoExecutionAlways
method will be executed after both successful and failed mojo
executions.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>