Improve Error Logging & Line Number Traceability in SAS connector Parsing

Problem Statement
Currently, when parsing errors occur in the Manta SAS Connector, the logs do not provide sufficient details about the root cause. For Example

1. The error message often lacks the specific SAS code line number and the file name where the parsing failed.

2. In Certain cases (e.g., NullPointerException), no sas code snippet, correct file context or line number is shown at all.

3. If %include statements are involved, the reported error line is misleading (e.g., an error shown at line 80 of sample.sas even though the file itself has only 20 lines, becuase it includes other files)

This makes it extremely difficult to identify the true source of the problem.

Business Impact

1. SAS modules can consist of 20+ files.

2. Without precise file/ line references, engineers are forced to manually search through hundreds of lines of SAS code accross multiple files to locate the root cause.

3. Debugging becomes time-consuming, error-prone and inefficient, significantly slowing down lineage adoption and increase operational cost.

Expected Enhancement

We request the following improvements to the SAS connnector parsing error handling

1. Detail error context in logs

   • Always display the exact SAS file name and line number where the parsing failed.

   • Provide the offending code snippet

2. Consistent Error reporting for all Exception types

   • Even in NullPointerException or similar parsing failures, the log should indicate the file + line context that triggered the failure

3. Handling %include scenarios

   • Clearly distinguish between the parent sas file and the included SAS file where the issue actually occurs.

   • Report error location relative to the correct file name not just the top level driver SAS file

This enhancement will reduce the debugging time by pointing engineers directly to the correct file where failure occured.