### What changes were proposed in this pull request?
Introduced a new class `SqlScriptingException`, which is thrown during SQL script parsing/interpreting, and contains information about the line number on which the error occured.

### Why are the changes needed?
Users should know which line of their script caused an error.

### Does this PR introduce _any_ user-facing change?
Users will now see a line number on some of their error messages. The format of the new error messages is:
`{LINE:N} errorMessage`
where N is the line number of the error, and errorMessage is the existing error message, before this change.

### How was this patch tested?
No new tests required, existing tests are updated.

### Was this patch authored or co-authored using generative AI tooling?
No

Closes #47553 from dusantism-db/dusantism-db/sql-script-exception.

Authored-by: Dušan Tišma <dusan.tisma@databricks.com>
Signed-off-by: Wenchen Fan <wenchen@databricks.com>