Related files that aren't bsp data

[snake-biscuits]

.bsp files often ship w/ other, non .bsp files with metadata etc.

.map & .vmf source map files, used by the Level-Editor & Compiler(s)
.prt & .lin VIS information from compiling, used for debugging & compiling
.aas, .ain & .nm bot navigation maps & navmeshes
.nut & .gnut external scripting
.ent extra entities
.lmp & .bsp_lump external .bsp lump data
.rson a .json-like mapping of relevant scripts & their contexts (client, server etc.)
.raw tonemap LUT

and many others
bsp_tool currently tries to catch these extraneous files w/ a filename match
lots of these files reside inside other folders as part of the game or mod's filesystem

If we go ahead w/ #21, we'll have to deal with these files appearing in other archives

So if we want to have a robust tracking of relevant files to the .bsp, we should document this stuff better
Noting which formats expect / work with which files
The locations (relative to the filesystem) would also be helpful
We could even apply this documentation to packed assets (compiled map cubemaps etc.)

[snake-biscuits]

Not going to be looking at .rpak & .wad archives directly

It’s nice to know how to extract textures etc.
But bsp_tool isn’t really for rendering
Tho bsp_tool_examples does explore rendering
And visualising data really helps with debugging

Using external assets is an exercise for new tools
Having some documentation to help build those tools would be nice tho

[snake-biscuits]

See #117 for discussion on .gdi Dreamcast GD-ROM disc images
.eal, .prt & other files are also discussed