Feat: several improvments

[jgribonvald]

This is a small contribution comparing to required change. At least this provide (see commits for details):

• a customizable path configuration from environnent variable
• pom xml change for packaging
• use of logger instead of System.out.println or instead of wrinting "manullay" into a file
• log errors instead of using printStackTrace
• apply some charset enum instead of String
• some little improvments
• possibility to use a tomcat JDBC resource instead of the configurable JDBC connexion

[jgribonvald]

Warning this is again in a WIP state, more test are required to check if there isn't bug due to change

[jgribonvald]

After merged it would remains (like on other project) such change:

The remaining part that should be done into the project side is:

• creating an individual account on OSS Sonatype, for that Follow the offical doc
• configure the pom.xml with this content (See here for official doc):

  <scm>
      <connection>scm:git:ssh://git@github.com/karutaproject/karuta-backend_legacy.git</connection>
      <developerConnection>scm:git:ssh://git@github.com/karutaproject/karuta-backend_legacy.git</developerConnection>
      <url>https://github.com/karutaproject/karuta-backend_legacy.git</url>
      <tag>HEAD</tag>
  </scm>
  <distributionManagement>
    <snapshotRepository>
      <id>ossrh</id>
      <url>https://s01.oss.sonatype.org/content/repositories/snapshots</url>
    </snapshotRepository>
    <repository>
      <id>ossrh</id>
      <url>https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/</url>
    </repository>
  </distributionManagement>

• configure your ~/.m2/settings.xml (or on your maven path) with your jira account to be able to authenticate when publishing a new release

[jgribonvald]

So after several test in preproduction, we didn't have problems with.