[BUG] Fix failing JavaScriptSharedUtilTest test in main

[mgaffigan]

There's a failing test in main:

[junit] TEST com.mirth.connect.util.JavaScriptSharedUtilTest FAILED

[tonygermano]

This was introduced in #90 . Previously, the prettyPrint function which is used by the new code formatting functionality was only called from here:

engine/client/src/com/mirth/connect/client/ui/editors/BaseEditorPane.java

Line 1675 in 98dde20

generatedScriptTextArea.setText(JavaScriptSharedUtil.prettyPrint(element.getScript(false)));

The prettyPrint context was updated in the PR to indent with tabs to match what the code editor was already doing for auto-indentation. However, the failing tests are expecting pretty printed code to have 4-space indents.

We need to determine if there are any further effects besides the failing tests when tabs rather than spaces are used for indents in generated scripts (potentially in the generated code that would be seen when errors are thrown from the javascript code or when running the channel in debug mode.)

An alternative could be to revert the indent change so that it produces spaces again, and change the editor to also use 4-space indents rather than tabs.

This was probably an overlooked inconsistency that the editor and prettyPrinter used different indents.

[mgaffigan]

generatedScriptTextArea.getText() is never called, so I don't see how this could escape to the server. JavaScriptSharedUtil.prettyPrint is not referenced by server or any plugins - so it seems like a UI-only issue.