SQLExecutorJob should fail if the result file cannot be written

Current Situation

• When the SQLExecutorJob is configured to use the resultset_as_variables=CSV and the result file can't be written, then job does not throw any exception and ends with a success status.

Desired Behaviour

• The SQLExecutorJob should throw an exception when the result file can't be written.

Test Instructions

• Configure the SQLExecutorJob to use the resultset_as_variables=CSV
• result_file = <file-path>
  • use the local and network share paths.
• Test the success and failure cases.