Add element print in release

[lukasdreyer]

Closes #1912

Describe your changes here:
Sometimes, weird stuff only happens in Release mode.
In order to manually find the error with print statements, this PR helps by introducing a print function that is available in release.

I am also open to just have one implementation, that works in both modes but only prints with DEBUG priority.

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 0% with 16 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.00%. Comparing base (c5e2676) to head (f6c2e8a).

Files with missing lines	Patch %	Lines
...mes/t8_standalone/t8_standalone_implementation.hxx	0.00%	8 Missing ⚠️
...t8_default/t8_default_common/t8_default_common.hxx	0.00%	4 Missing ⚠️
src/t8_schemes/t8_scheme.cxx	0.00%	2 Missing ⚠️
src/t8_schemes/t8_scheme.hxx	0.00%	2 Missing ⚠️

Additional details and impacted files

@@                          Coverage Diff                          @@
##           enhancement-standalone_type_uint8    #1910      +/-   ##
=====================================================================
- Coverage                              76.15%   76.00%   -0.15%     
=====================================================================
  Files                                    103      103              
  Lines                                  19424    19470      +46     
=====================================================================
+ Hits                                   14792    14798       +6     
- Misses                                  4632     4672      +40     

☔ 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]

An alternative approach is suggested in PR #2033
If this fixes you issue, too, please close this PR.

[spenke91]

You said in the description that you're open to have a combined function for debug and release. Without having looked much into it, this seems like the much cleaner option to me too.
But maybe there are reasons I am not aware of yet that made you go for the two separated functions in this first version of the PR? 🤔 Could you comment on that?

[spenke91]

Suggested change

	* Print a given element. For a example for a triangle print the coordinates
	* and the level of the triangle. This function is only available in the
	* debugging configuration.
	* Print a given element. For a example for a triangle print the coordinates
	* and the level of the triangle.