Improvement: Curved tutorial meshes

[sandro-elsweijer]

Closes #2161

Describe your changes here:
The curved tutorial meshes were broken. I adapted the geometries and meshing parameters so that the meshes look better and are not broken.

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. Make sure to add a file documentation for each file!
• 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

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.25%. Comparing base (98a2c07) to head (43087e5).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2151   +/-   ##
=======================================
  Coverage   78.25%   78.25%           
=======================================
  Files         114      114           
  Lines       19050    19050           
=======================================
  Hits        14907    14907           
  Misses       4143     4143           

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

[spenke91]

I tried the tutorial and it mostly worked fine for me. However, I ran into some problems with tetrahedra. Without VTK library, the mesh looked like this:

with VTK library:

I guess it is related to this error message I got:

Do you already know what is causing this? :-)

Also, I took the freedom to change the autoconf options mentioned in the wiki to their CMake counterparts, I guessed you wouldn't mind. Lastly, it may be worth noting that the output created with the VTK library required me to use a newer paraview version than 5.10. Maybe it's worth noting somewhere in the tutorial that users may run into this problem?