Write multi-target import tests 🆒

[EthanThatOneKid]

Tests need to be written to validate that generated modules are being properly imported by the target language's compiler for each target language available. Testing other language targets than TypeScript require prerequisite installations 🆗.

• [ ] Go: Review the process that the go get subcommand undergoes in order to properly import a dependency to a Go project. Make sure that this process is compatible with the Fart server (GET /go/path/to/mod). See Self-hosted ‘go get’-able repos HOWTO.
• [ ] TypeScript: Verify that the generated types are imported accurately by Deno (on GET /ts/path/to/type.ts) and Node (on GET /node/path/to/type).
• [ ] C++: The easiest thing to do is merely generate static header files and import them into a C++ file that way.
• [ ] QB64: Research how libraries and structs are defined in QB64 and how each source file is taken into account by the QB64 compiler. Make sure the generated types are compatible with QB64 compilation.

[EthanThatOneKid]

For now, Deno allowed for the importation of generated Fart files to be trivial and attainable at no cost. In order to spin up a Go-equivalent, we would need to spin up our own gomods/athens instance on Digital Ocean or something. For this reason, the Fart CLI can be used for non-TypeScript projects. This means that in order for Go to integrate with Fart, Fart's file generation must be integrated into that project's build process via the Fart CLI. The generated Fart files can be ignored by adding *.generated.go to the repo's .gitignore.