Canonical loading of location4j.bin file from classpath

[tomaytotomato]

fixes #9

Ensures the binary file is located and loaded from the jar before anything else, or any other file with same name.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[jottinger]

I know this is closed, but I don't think this actually solves the problem. To test, you could put another jar with "/locations4j.bin" or whatever the filename is in front of the locations4j.jar file (thus, earlier in the classpath) and see if the right data is present; I think this is going to load the file in classpath order. You could get the URL from findResource and compare the schema (which would show the jar file) and if they don't match, fail (this is a suggestion from ernimril on IRC, not me); you could also measure the impact of parsing the json and just deliver it in text format (or compress it, as I'd also suggested) which would avoid the whole "serialization is a giant security hole through which battleships could sail easily" problem.