Package (re)naming for the latest release

Hi,

it looks like that in the latest release of sshj, the groupId of the artifact has been changed to _com.hierynomus_, but the library maitains the old package naming of _schmizz.net_, breaking the [1-1 correspondance between the Maven {groupId, artifactId} pair and the Java package name](http://wiki.apache.org/commons/MavenAndClasspath).

e.g.: when an old version of sshj is a transitive dependency in a project that use the latest com.hierynomus:sshj, maven treats them as different libraries, putting both of them in the classpath without rising any conflict alert, but since the share the same package naming, only one of them will be actually usable on runtime (and may lead to unexpected behavior).