Bench for SQL scan / where

[mamcx]

Description of Changes

• Bench for SQL queries: SELECT * FROM table / SELECT * FROM table WHERE pk = value
• Instrument calls for tracy
• Add tracy support in run_standalone_temp.sh

API and ABI

• This is a breaking change to the module ABI
• This is a breaking change to the module API
• This is a breaking change to the ClientAPI
• This is a breaking change to the SDK API

If the API is breaking, please state below what will break

[joshua-spacetime]

LGTM!

[kazimuth]

This PR broke the module benchmarks, FWIW. There is also a way to structure it that wouldn't have caused the issue. I would have appreciated if you had waited for my review.

[mamcx]

So, what should I do instead?

[kazimuth]

Rather than adding trait methods to BenchDatabase, it would be best to add a separate file spacetime_sql.rs with a new struct SpacetimeSQL : BenchDatabase that measures database access via the SQL API. This new file could use TableSchema for TableId.

This means that each generic benchmark implementation is measuring a separate access path to the database. Times of the SQL api will be clearly separate from times of reducer calls.

The specific thing that broke here is that a PascalCase name has been used instead of a snake_case due to the refactoring in this branch, here: https://github.com/clockworklabs/SpacetimeDB/pull/370/files#diff-6179b2533c85dd1dc6d18d56e1bff1a01fb6c4dfcd2861a08d7ea565ad1f02fbR192

I'm working on a branch that reverts this, so that benchmarks will run on master. Then I'll start a new PR to add the spacetime-SQL benches, we can collab on that :)

(We'll need to have no-ops for insertion benchmarks there, in some way. I guess we'll need to add an insertion_supported() -> bool method to BenchDatabase.)