Regenerating configs

[OpenBagTwo]

GIVEN Alex sees that EnderChest supports new functionality that's controlled via newly introduced keys set within the enderchest.cfg or shulkerbox.cfg files

WHEN she runs the command

$ enderchest reload [enderchest | shulker_boxes | shulker_box <box_name>]

THEN EnderChest will open, validate and rewrite all config files (or just the chest configuration / specified box config) in the latest format

SO that she's not going in blind trying to set the key values and leverage the new features

Notes

• This could be done by default every time a config is read EnderChest reads in a file, and it could be done intelligently by checking against the version set in the properties tag
• This could be done interactively if the user doesn't specify what should be reloaded
• This could also check instances (but only if Enderchest gather minecraft deletes manually added tags #54 is resolved first) and remotes, though this should not be done by default
• This should also (optionally) check that each remote's alias in enderchest.cfg matches the remote chest's name property (see: EnderChest remote aliases should match their names #146)