FoxNapRPG should automatically detect and use spec files

[Gili Barlev]

If the FoxNapRPG executable is run in the same directory as a spec file (see notes), it should automatically attempt to parse and load it (if it can't be parsed, the executable should emit a warning--which for most users won't be seen).

Notes

• The file should be named "FoxNapRPG"...
• ... with any of the supported extensions:

  FoxNap/foxnap_rpg/config.py

  Lines 29 to 32 in b5aa119

         - INI (.ini, .cfg, .config, .conf) 
         - JSON (.json) 
         - CSV (.csv, .tsv) 
       - This method will attempt to read files ending in no extension or .txt as INI. 

• The filename should be case-insensitive
• In the event that multiple matching files are present:
  • FoxNapRPG should emit a warning (again, will mostly not be seen)
  • FoxNapRPG should attempt to parse each, one by one, until one is parsed successfully (warn again on each failed parse)
  • The canonical CamelCased "FoxNapRPG" file name should be preferred ahead of all-lowercase. Beyond that, the ordering need only be deterministic (python sorted is fine)

While I meant to include this in the original design, I still think use of spec files is going to be a niche use-case, and the docs don't even include example configs. That is all to say: this need not be part of the initial release.