Feature benchmark search

[lukasdreyer]

Closes #1920

Describe your changes here:
Playground for search benchmark

All these boxes must be checked by the AUTHOR before requesting review:

• The PR is small enough to be reviewed easily. If not, consider splitting up the changes in multiple PRs.
• The title starts with one of the following prefixes: Documentation:, Bugfix:, Feature:, Improvement: or Other:.
• If the PR is related to an issue, make sure to link it.
• The author made sure that, as a reviewer, he/she would check all boxes below.

All these boxes must be checked by the REVIEWERS before merging the pull request:

As a reviewer please read through all the code lines and make sure that the code is fully understood, bug free, well-documented and well-structured.

General

• The reviewer executed the new code features at least once and checked the results manually.
• The code follows the t8code coding guidelines.
• New source/header files are properly added to the CMake files.
• The code is well documented. In particular, all function declarations, structs/classes and their members have a proper doxygen documentation.
• All new algorithms and data structures are sufficiently optimal in terms of memory and runtime (If this should be merged, but there is still potential for optimization, create a new issue).

Tests

• The code is covered in an existing or new test case using Google Test.
• The code coverage of the project (reported in the CI) should not decrease. If coverage is decreased, make sure that this is reasonable and acceptable.
• Valgrind doesn't find any bugs in the new code. This script can be used to check for errors; see also this wiki article.

If the Pull request introduces code that is not covered by the github action (for example coupling with a new library):

• Should this use case be added to the github action?
• If not, does the specific use case compile and all tests pass (check manually).

Scripts and Wiki

• If a new directory with source files is added, it must be covered by the script/find_all_source_files.scp to check the indentation of these files.
• If this PR introduces a new feature, it must be covered in an example or tutorial and a Wiki article.

License

• The author added a BSD statement to doc/ (or already has one).

[codecov]

Codecov Report

❌ Patch coverage is 81.97674% with 62 lines in your changes missing coverage. Please review.
✅ Project coverage is 75.90%. Comparing base (4702303) to head (769afe0).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/t8_forest/t8_forest.cxx	16.12%	26 Missing ⚠️
src/t8_forest/t8_forest_iterate.cxx	31.57%	13 Missing ⚠️
...mes/t8_standalone/t8_standalone_implementation.hxx	95.57%	12 Missing ⚠️
...rc/t8_forest/t8_forest_search/t8_forest_search.cxx	42.10%	11 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1919      +/-   ##
==========================================
+ Coverage   75.77%   75.90%   +0.12%     
==========================================
  Files         103      103              
  Lines       19230    19521     +291     
==========================================
+ Hits        14572    14817     +245     
- Misses       4658     4704      +46     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Davknapp]

A lot of the changes are based on development done in #1443. We should merge that one first, in my opinion.

[Davknapp]

This is a file, that does not belong into t8code in my opinion. You can use it in t8data and cite t8data to make research-results reproducable.