Fix incorrect check of InvalidFieldException to InvalidFieldFault while generating MSQ Error Report

[gargvishesh]

InvalidFieldFault is incorrectly checked as InvalidFieldException in mapQueryColumnNameToOutputColumnName. Fix it to the correct check. Also added test for the generated exception as part of RowBasedFrameWriterTest.

Verified the generated MSQErrorReport by raising an empty RuntimeException inside StringFieldWriter.writeTo() in a custom build.

[LakshSingla]

Can we add any unit tests here? It feels weird that we have to test it in a separate custom build to generate the exception. Can you mention where you are throwing an exception to test this flow? It'd be prudent to add a unit test that throws in the same flow to test this exception.

[gargvishesh]

Have added RowBasedFrameWriterTest for the generated InvalidFieldException.

[LakshSingla]

I think we should revert this change, and look for a way to generate the exception using the class's public methods (#11848 (comment)), if possible. Since the code coverage is still not satisfied, I think we can remove the new test added (since that isn't testing the actual code in the ControllerImpl where everything is bubbled up to) and merge it as is, since it's a fairly low risk change

[gargvishesh]

Thanks for the comment and the reference. Using a public method now instead.

[LakshSingla]

Failures are unrelated. Thanks for the PR 🚀