[evals] tracking issue for a solution for storing and analyzing vally runs

Our azd eval work uses Vally, but we do not have a solution for storing results across runs and analyzing trends, statistics, and regressions. There are a few internal projects, but we'd prefer to to use a vally supported output so we can analyze for trends, and keep track of some basic metrics like whether tests are consistently passing, etc...

There is an issue for this in vally, so this issue is just to provide a placeholder we can use in our planning:

"Support pluggable vally ingest destinations beyond SQLite (e.g. Kusto/ADX)"
* microsoft/vally#575: https://github.com/microsoft/vally/issues/575