Configure file reader for records.json

[KennyTill]

configure location, parse through, pick out pieces of information that are actually important, and ignore the rest. Dump into list of some type, and query happens in memory.

Likely information needed:

• track name
• artist/chart maker name (there is no standard on what information is put here)
• track id (may need to do a file scan at startup to see if the ID still exists, file may have been deleted. In game
• list of difficulties, as string
• track length (further investigation required to see if this is in the json)

[KennyTill]

Changing over to directory based scan, but fulfills the basic end goal of this issue closed by b5717de4fd3e467e8992307140cfbd42b42fcd13