Improve sqllogictest error reporting

[gabotechs]

Which issue does this PR close?

• Closes #.

Rationale for this change

Improve the way errors get shown to the developer while running sqllogictests.

What changes are included in this PR?

• Canonicalizes the path of the file that contains an error in a sqllogictests, so that when reporting the error in the following format: "{path}:{line_number}" its clickable from IDEs, pointing directly to the exact line containing the failing test (verified on RustRover)
• Runs all the sqllogictests in a single file even if some of them fail, reporting the first 10 failures, instead of just the first one.

Example output after intentionally introducing 3 failures in aggregate.slt:
Before:

External error: query result mismatch:
[SQL] select array_sort(c1), array_sort(c2) from (
  select array_agg(distinct column1) as c1, array_agg(distinct column2) ignore nulls as c2 from array_agg_distinct_list_table
);
[Diff] (-expected|+actual)
-   [NULL, b, w] [[0, 1], [0, 1]]
+   [NULL, b, w] [[0, 1], [1, 0]]
at test_files/aggregate.slt:313

After:

External error: 3 errors in file /Users/foo/github/datafusion/datafusion/sqllogictest/test_files/aggregate.slt

1. query result mismatch:
[SQL] select array_sort(c1), array_sort(c2) from (
  select array_agg(distinct column1) as c1, array_agg(distinct column2) ignore nulls as c2 from array_agg_distinct_list_table
);
[Diff] (-expected|+actual)
-   [NULL, b, w] [[0, 1], [0, 1]]
+   [NULL, b, w] [[0, 1], [1, 0]]
at /Users/foo/github/datafusion/datafusion/sqllogictest/test_files/aggregate.slt:313


2. query result mismatch:
[SQL] SELECT bit_or(c5), bit_or(c6), bit_or(c7), bit_or(c8), bit_or(c9) FROM aggregate_test_100
[Diff] (-expected|+actual)
-   -1 -1 255 65534 4294967295
+   -1 -1 255 65535 4294967295
at /Users/foo/github/datafusion/datafusion/sqllogictest/test_files/aggregate.slt:416


3. statement is expected to fail with error:
	(regex) DataFusion error: Random failure
but got error:
	DataFusion error: This feature is not implemented: VAR_POP(DISTINCT) aggregations are not available
[SQL] SELECT var_pop(c2), var_pop(distinct c2) FROM aggregate_test_100
at /Users/foo/github/datafusion/datafusion/sqllogictest/test_files/aggregate.slt:584

Are these changes tested?

These are changes to how the tests are reported, so I suppose?

Are there any user-facing changes?

No

[Omega359]

Runs all the sqllogictests in a single file even if some of them fail, reporting all failures, instead of just the first one.

I would prefer it to be limited to say the first 10. Otherwise this looks good.

[gabotechs]

I would prefer it to be limited to say the first 10. Otherwise this looks good.

👍 no strong opinion here, I imagine that if more than 10 tests fail, it means that something went really wrong

[alamb]

I would prefer it to be limited to say the first 10. Otherwise this looks good.

👍 no strong opinion here, I imagine that if more than 10 tests fail, it means that something went really wrong

yeah I agree limiting the error messages to some reasonable limit would make for a better experience

[gabotechs]

👍 Done! also added some failure indexes to help our eyes parse the different errors quickly

[gabotechs]

Just so that people have a bit more context about why is this PR coming suddenly out of the blue, I'm exploring this idea that implies adding a new sqllogictest runner that, to the surprise of no one, results in a massive amount of failures.

I'm using the contents of this PR to better triage the errors that I see there, but I'm keeping this as a separate PR as I imagine this can be useful regardless of whether my experiment turns out to be a good idea or not.

[2010YOUY01]

Thank you. I think it's good to go after fixing the CI.

[2010YOUY01]

Suggested change

	async fn run_file_in_runner<D: AsyncDB, M: MakeConnection<Conn = D>>(
	/// Run the test file specified by `path` using the provided runner.
	/// Only first `ERRS_PER_FILE_LIMIT` errors will be displayed.
	async fn run_file_in_runner<D: AsyncDB, M: MakeConnection<Conn = D>>(

[alamb]

🚀