Fix the additional string leaks detected with --baseline

Skipping dead code elimination leaves the array debugging calls to chpl__testPar
in the code (while the contents of this call would never be exercised because of
the appropriate boolean flag, the call is still made).  Since these calls send
in a message in the form of a string, additional memory leaks are generated.
To combat that, we now cast the message to our new string record - this seemed
fine because 1) only developers use chpl__testPar or baseline to our knowledge,
and 2) ChapelStandard already includes the NewString module so the cast was the
only thing that needed to be added.  When the string record is our default, this
cast will no longer be necessary and should be removed.
Merge pull request #747 from lydia-duncan/baselineStringLeaks

Fix the additional string leaks detected with --baseline

Skipping dead code elimination leaves the array debugging calls to chpl__testPar
in the code (while the contents of this call would never be exercised because of
the appropriate boolean flag, the call is still made). Since these calls send
in a message in the form of a string, additional memory leaks are generated.
To combat that, we now cast the message to our new string record - this seemed
fine because 1) only developers use chpl__testPar or baseline to our knowledge,
and 2) ChapelStandard already includes the NewString module so the cast was the
only thing that needed to be added. When the string record is our default, this
cast will no longer be necessary and should be removed.