feat(small): Support <slt:ignore> marker in sqllogictest for non-deterministic expected parts

[2010YOUY01]

Which issue does this PR close?

Part of #17612

Rationale for this change

sqllogictests are in general easier to maintain than rust tests, however it's not able to test EXPLAIN ANALYZE results, because their results include changing part:

(in datafusion-cli) The elapsed_compute measurement changes from run to run.

> EXPLAIN ANALYZE SELECT * FROM generate_series(100);
+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| plan_type         | plan                                                                                                                                                                                             |
+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Plan with Metrics | LazyMemoryExec: partitions=1, batch_generators=[generate_series: start=0, end=100, batch_size=8192], metrics=[output_rows=101, elapsed_compute=74.042µs, output_bytes=64.0 KB, output_batches=1] |
|                   |                                                                                                                                                                                                  |
+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row(s) fetched.
Elapsed 0.006 seconds.

We can add a special marker to sqllogictest to skip those non-deterministic parts.

What changes are included in this PR?

• Changed sqllogictest validator to recognize <slt:ignore> marker
• doc
• slt test

Are these changes tested?

Are there any user-facing changes?

[martin-g]

This early return would make it hard to debug. It would be nice to log a warning with the reason, as done below (line 116+).

[martin-g]

Suggested change

	Sometimes parts of a result change every run (timestamps, counters, etc). To keep the rest of the snapshot checked in, replace those fragments with the `<slt:ignore>` marker inside the expected block. During validation the marker acts like a wildcard, so only the surrounding text must match.
	Sometimes parts of a result change every run (timestamps, counters, etc.). To keep the rest of the snapshot checked in, replace those fragments with the `<slt:ignore>` marker inside the expected block. During validation the marker acts like a wildcard, so only the surrounding text must match.

[martin-g]

I think this logic won't detect a prefix in the actual_snapshot.
Let's say the first expected fragment is "Hello" but the actual_snapshot starts with "Anything here before Hello". The find() will set the position to the correct index but Anything here before will be ignored and assumed as matching.
Similar issue with a suffix in actual_snapshot.