Redesign models/entitites for localization

[magicDGS]

At least for the sets, there are currently some concepts that are mixed together in the models and entities:

• Translations for the names and other fields worth translating.
• Region-specific information, as the set-code that might contain the region code too

We must either separate this 2 concepts to have proper localization format that is able to provide a good usage for:

• Single language representation of the models
• Easy lookup of values on the JSON
• Clear design easy to understand

The problen with the region data is that it is difficult to consolidate to be able to identify the language that the region belongs to, unless the mapping is clear between the key and the language the region belongs to. An example for the mess is the Legend of Blue Eyes White Dragon, where:

• English releases are in 4 versions (world, NA, EU, OC) or 5 if counting Asian-English. Nevertheless, even if each region was released in a different date, the konami-ID is the same (except for Asian-English)
• French has 2 versions (France and Canada). Nevertheless, the same konami-ID is present for France. The setCode is the same in both of them because it is more related with the language than with the region (compacting the data might not be possible)

[magicDGS]

Some approach could be:

1. Following a similar approach as the Konami DB, separating the TCG/OCG regions (will fix at the same time #113), and within each region have both translations and region data.
2. Following a similar approach as yugipedia, separating translations (i.e., names) from set-information region data (which uses the prefix for the different regions as appearing on the prints.
3. Hybrid approach, where the separation between TGC/OCG regions is created, but keeping outside the translations.