test(taps): Add benchmark test on map transforms via pytest-benchmark

[haleemur]

relates to #2002.

As suggested in #2002 (comment),

This PR adds a benchmark test using pytest-benchmark to test the performance of stream maps using simpleeval, and ensure that we do not harm application performance by using EvalWithCompoundTypes.

The PR does the following:

• separate some logic into function _run_transform out of _test_transform to use for benchmarking
• add a benchmark test for the repositories stream with stream size of 4000 records
• add pytest-benchmark as a development dependency
• add nox session for benchmarking (benches)

I'm less sure if I've implemented the following two correctly as I'm not familiar with github actions

• add `benches to the github-actions workflow matrix
• add action to upload benchmark results

---

📚 Documentation preview 📚: https://meltano-sdk--2011.org.readthedocs.build/en/2011/

[haleemur]

@edgarrmondragon I added the benchmark test, but having some trouble with the github action to post the benchmark result as a comment on the PR

for now, am removing the gh action to try to comment on the PR

[codecov]

Codecov Report

Merging #2011 (28da357) into main (2dc27fc) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2011   +/-   ##
=======================================
  Coverage   87.42%   87.42%           
=======================================
  Files          59       59           
  Lines        5136     5136           
  Branches      830      830           
=======================================
  Hits         4490     4490           
  Misses        451      451           
  Partials      195      195           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[edgarrmondragon]

@edgarrmondragon I added the benchmark test, but having some trouble with the github action to post the benchmark result as a comment on the PR

for now, am removing the gh action to try to comment on the PR

Thank you so much for the contribution @haleemur! I think this is good enough as a first iteration. I think I can integrate Codspeed with very minor changes to comment in PRs.