Add support for the Legacy Bounty Hunter minigame

[dmeredith96]

This PR adds support for the Legacy Bounty Hunter minigame and fixes the stat fetching part of the API. INVALID_FORMAT_ERROR will no longer be thrown.

Tests were also updated.

Fixes issue #75

[evanw555]

Thanks for taking the time to address the API change, however I'd strongly urge you to consider the compatibility implications of this approach. By creating new keys (hunterLegacyBH, rogueLegacyBH) for the "legacy" activities and reassigning the old keys (hunterBH, rogueBH) to the new activities, you will likely cause data corruption in any applications using this library.

For instance, my application tracks user skill/boss data and saves it to a Postgres database using the keys defined in this library. If it were to track BH activity data as well, then adopting this change would cause all the existing data to be incorrectly interpreted as "new" bounty hunter data unless all the data is manually migrated from the old format to the new format.

It would be much safer to keep the old keys and instead create new keys for the new activities e.g. hunterBH2. I know the naming wouldn't be ideal, but this is a best-practice approach.

[dmeredith96]

Thanks for taking the time to address the API change, however I'd strongly urge you to consider the compatibility implications of this approach. By creating new keys (hunterLegacyBH, rogueLegacyBH) for the "legacy" activities and reassigning the old keys (hunterBH, rogueBH) to the new activities, you will likely cause data corruption in any applications using this library.

For instance, my application tracks user skill/boss data and saves it to a Postgres database using the keys defined in this library. If it were to track BH activity data as well, then adopting this change would cause all the existing data to be incorrectly interpreted as "new" bounty hunter data unless all the data is manually migrated from the old format to the new format.

It would be much safer to keep the old keys and instead create new keys for the new activities e.g. hunterBH2. I know the naming wouldn't be ideal, but this is a best-practice approach.

Fair call out, can make that change tonight.

[evanw555]

The new naming looks good to me. Hopefully we can get this approved and merged soon, my application has been down for a few days and users are getting anxious

[maxswa]

Apologize for the delay! I'll be publishing this ASAP