test: add vectorizer benchmark tools

[alejandrodnm]

New benchmark just recipes for the vectorizer:

• just pgai benchmark-mem: runs the vectorizer on a queue of 500
  items, generates a memray profile, and a memory usage flamegraph.

• just pgai benchmark-cpu: runs the vectorizer on a queue of 500
  items, generates a CPU usage flamegraph using py-spy.

• just pgai benchmark-cpu-top: runs the vectorizer on a queue of 500
  items, displays a top like interface of CPU usage.

• just pgai benchmark-queue-count: shows the queue count of the
  running benchmark. Should be executed in a separate terminal. The
  count is updated in an interval.

The benchmark DB uses the wiki.dump stored in the repository, creates an
openAI vectorizer, and runs the benchmark tool storing the results in
projects/pgai/benchmark/results.

There's a new command for the cli pgai vectorizer worker-benchmark.
It's the same as the regular worker, but it's wrapped in a vcr client
that replays openAI requests. This command is used by the CPU benchmarks
in order to have constant request/response times to the API, and have
more deterministic time results. The cassette file is tracked using
git-lfs.

Memory benchmarks don't use the vcr wrapped command because they pollute
VCR will use considerable memory to handle the API calls.

https://www.loom.com/share/5538c8fa4bb243d88a246ca6b82e7cc7?sid=89bf1ed6-8def-4e6e-8fb2-711f42660b7f

https://www.loom.com/share/733fca2f5008460f9d763a72544db5fb?sid=e56f1a72-69f3-41c8-9b3f-36f859f556fc

[JamesGuthrie]

Why did this change?

[alejandrodnm]

I'm reverting it back, I updated it for a test.

We are using 3.12 for the docker container and I wanted the same,

[alejandrodnm]

@JamesGuthrie I moved the part of vcr to the benchmark repo, and updated the recipes and create_vectorizer.sql to be more customizable.