KSPBurst should not store outputs in KSP_x64_Data because it can be shared across instances with CKAN

[JonnyOThan]

CKAN introduced a system where you can symlink stock files across instances. Therefore KSPBurst should not store per-instance output in there.

I hit this when running more than one such instance at a time:

[LOG 10:17:57.333] [KSPBurst]: Burst stdout:
[EXC 10:17:57.336] UnauthorizedAccessException: Access to the path "C:/Program Files (x86)/Steam/steamapps/common/KSP Stripped/KSP_x64_Data\Plugins\lib_burst_generated.dll.bak" is denied.

[Phantomical]

Some notes here from digging into this:

• There is a LoadAdditionalAssembly method but it is only supported on 2020.1 and later.
• Otherwise unity hardcodes that location in KSP_x64_Data

I don't think it is actually possible to work around those issues. This issue may actually just be unsolvable.

[Dalewyn]

Symbolic links are a very advanced file system feature that the average user would practically never use (Windows has no GUI frontend for this and Linux users are not average), so I think a complication introduced by CKAN rather than KSP or Unity is beyond the scope of a mod.

TL;DR: This is a CKAN issue, with room to debate if CKAN is overstepping its bounds as a mod manager (that discussion is certainly beyond the scope of this repo!).