Extend validation to benchmark performance runs as well

[GregoryKimball]

We must allow cached comparison results. 1K, 3K, 10K will be too expensive to recompute the reference result every time.

[GregoryKimball]

As of March 9, there is a script in velox-testing to create validated results via DuckDB, and a script to take current run and compare with DuckDB. These scripts do not run automatically.

We need a pattern to store validated results from DuckDB and probably a pattern to store results for each benchmark run under the "tag" folder. As the results are saved, we need to compare the two files.