Image Map Renderer

Rewrote backend

3 years ago when i initially wrote this plugin, I had no sense of what good code was whatsoever

This overhaul is to remedy that, here are some things that are new:

- no more data.yml Minecraft maps are stored via their 'id' (which is the number you see when you hover over the map item). Prior to this update, a data.yml file was created to store each id managed by the plugin and the file path to its corresponding image. This was just straight up bad... for one you couldn't move the server to another part on the computer without manually updating the file paths.. secondly, it's just dumb, you can easily store the id in the file name Thank you to SlyCedix for pointing this out to me

- optimized image storage Maps in Minecraft are always rendered at a resolution of 128x128, hence making it pointless to store any image of higher res to that. Hopefully this change can reduce the storage requirement by a good amount

Many things have changed on the backend and hopefully it should lead to a more optimized experience overall (at least a little bit)