Fixes issues with migration from V2

[sarhatabaot]

Fixes #364

• Fixed an issue with reading old FishReports. (Created a new class LegacyFishReport)
• Ensured the connectionfactory is initialized even when using V2.
• Ensured flyway migration are run when using /emf admin migrate
• Improved how we check for V2.

Table Prefix

• [x] Added table prefix

Changed configuration to improve readability:

• You can now rename your sqlite database.
• Removed experimental features and added a warning to database:

  # WARNING EXPERIMENTAL: This feature is experimental and may not work properly.
  # The plugin stores stats about fish caught by players, used in the fish log. Disabling this will disable functionality
  # of this feature.
  # ATTENTION: Toggling this requires a full server restart.
  database:
  enabled: false
  # Available option are: mysql, sqlite
  type: sqlite
  # The address of the database
  # (the port 3306 is automatically added in by default, if different: specify with address:port)
  address: localhost
  # The name of the database to store fish data in
  database: evenmorefish
  # The table prefix for the database.
  # WARNING: Changing this will create new tables in the database.
  # Only use this during first setup or before migrations.
  # (Or after, but only if you know what you're doing).
  table-prefix: "emf_"
  # Login information
  username: root
  password: ''

• Added an enabled config entry to database instead of experimental features.
• Added database type to make it more clear what type we are using (mysql, sqlite)

Note about migration from v5 ->

I had an issue while implementing this, since we added some migrations prior to v4. Flyway community doesn't support this functionality, so we're actually dropping the table, and then running migrations from version 5 (not including) onwards. So v6.0, v6.1 etc

Tests

• [x] V2 -> V6.1
• [x] V5 -> V6.1
• [x] New install -> V6.1