Extension must be portable

[Ansible2]

For performance and brevity the current goal will be to cutdown on the number of files in the end package. This may be accomplished in by two means:

• Packaging the JavaScript files for the server, client, and grammars into individual .js files or single file if possible.
• Taking all the markdown files and shrinking them down into either a single JSON object or multiple for each doc section.

Acceptance Criteria:

• The extension can be used by anyone outside of debug mode in the repository

[Ansible2]

NOTE:

• Documentation should be available in sqf.syntax.* during runtime.
• However, it needs to be compiled into JSON or JS during build time, likely in the build.ts.

There needs to be some means of referencing the correct data in the sqf.syntax.* before building the files.

This could mean using a separate file that is built with another package script that can be run independently of the build script. It can generate a .ts file that creates a map of all of the docs and their contents, this is then just transpiled like the rest of the ts files.