add benchmarks for get_for_dialect

[markus-96]

these are high-level-benchmarks that will somehow call Field.get_for_dialect

Description

The above mentioned method has some potential to be optimized.

Motivation and Context

I want to optimize the method, like in this comment: #1859 (comment)

It is not used very often, but for example if you call any tortoise.expressions.Function, filter through/retrieve values of related models,...

How Has This Been Tested?

there seams to be a slight improvement with my optimizations

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added the changelog accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codspeed-hq]

CodSpeed Performance Report

Merging #1862 will not alter performance

_{Comparing markus-96:benchmark-get_for_dialect (ad1e48b) with develop (3a5e836)}

Summary

✅ 8 untouched benchmarks
🆕 4 new benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
🆕	test_expressions_count	N/A	972.7 µs	N/A
🆕	test_expressions_f	N/A	849.4 µs	N/A
🆕	test_field_attribute_lookup_get_for_dialect	N/A	621.9 µs	N/A
🆕	test_relations_values_related_m2m	N/A	1.2 ms	N/A

[coveralls]

Pull Request Test Coverage Report for Build 13008190876

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 89.423%

---

Totals
Change from base Build 12927974311:	0.0%
Covered Lines:	6494
Relevant Lines:	7079

---

💛 - Coveralls

[henadzit]

This one doesn't have .annotate but it is located in the test_annotate. Maybe, move to test_filter.py?

[markus-96]

moved it to test_relations.py for now. Maybe we can add more tests benchmarking relational behaviour in the future

[henadzit]

All the functions in this file are going to be the names of the benchmarks, so it would be nice to name them well:

• test_annotate_with_count
• test_annotate_with_decimal
• etc.

[markus-96]

test_annotate.py was a working title I did not change yet, sorry for that. I simply wanted some functions that call get_for_dialect, so I went ahead and looked where the function is used, placed a 1/0 before/after the function call, ran make ci and hoped that an error is thrown somewhere. Then, I copied these "failing" tests and adopted them as a benchmark. Duriung this, I skipped everything in schema_generator.py because this is only executed once during startup and would not benchmark any real-world scenario.

[henadzit]

Looks good to me!