Separate file for the #FORM blocks

[krowvin]

Consider adding the ability to also load a file in.

If you have HTML in your #FORM content, for example, this will break:

• Syntax highlighting for that given file type (i.e. CSV/HTML/etc)
• Linting for HTML, CSS, JavaScript if it is HTML
• Autoformatting based on filetype

Consider making this backwards compatible. Perhaps have the form builder check if #FORM is present and if not run the file normally. Then provide a class/constructor for reading template files that load them in as is.

Could use a template engine like handlebars but would probably be fine keeping it as is so we do not have to convert reports. People can just chose if they want to strip that current #FORM content into another file.

[krowvin]

@DanielTOsborne do you have a means of testing this or will the automated checks be enough for this?

I tested against our current report for both #FORM and #FORMFILE

Edit: I created #28 for automated testing for data