Add AnalysisSurfaceIntegral

[Arpit-Babbar]

This PR adds a callback to compute forces on the surface of a body, like the surface of an airfoil. Three examples, each having steady state solutions, have been added

1. A transonic flow over NACA0012 using Compressible Navier-Stokes code. This is the most convincing because I have matched values with Table 3 of this paper
2. A flow over NACA0012 airfoil using Compressible Euler code having AMR.
3. Subsonic flow over cylinder.

[github-actions]

Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

• The PR has a single goal that is clear from the PR title and/or description.
• All code changes represent a single set of modifications that logically belong together.
• No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

• The code can be understood easily.
• Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
• There are no redundancies that can be removed by simple modularization/refactoring.
• There are no leftover debug statements or commented code sections.
• The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

• New functions and types are documented with a docstring or top-level comment.
• Relevant publications are referenced in docstrings (see example for formatting).
• Inline comments are used to document longer or unusual code sections.
• Comments describe intent ("why?") and not just functionality ("what?").
• If the PR introduces a significant change or new feature, it is documented in NEWS.md.

Testing

• The PR passes all tests.
• New or modified lines of code are covered by tests.
• New or modified tests run in less then 10 seconds.

Performance

• There are no type instabilities or memory allocations in performance-critical parts.
• If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

• The correctness of the code was verified using appropriate tests.
• If new equations/methods are added, a convergence test has been run and the results
  are posted in the PR.

Created with ❤️ by the Trixi.jl community.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.32%. Comparing base (73da92c) to head (2810499).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1812      +/-   ##
==========================================
+ Coverage   96.30%   96.32%   +0.02%     
==========================================
  Files         441      445       +4     
  Lines       35799    35926     +127     
==========================================
+ Hits        34476    34605     +129     
+ Misses       1323     1321       -2     

Flag	Coverage Δ
unittests	96.32% <100.00%> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[DanielDoehring]

Thanks a lot for bringing this functionality to Trixi!

I added some first mostly implementation-related comments.

Please also add a test for the new elixir, such that the newly added code becomes part of our CI runs.

[JoshuaLampert]

Why is the formatter making so many changes? I get failing CI if I don't run formatter in all files.

See #1842.

[Arpit-Babbar]

Why is the formatter making so many changes? I get failing CI if I don't run formatter in all files.

See #1842.

Ah, thank you so much!

[andrewwinters5000]

I left a comment to open a discussion on how to grab the boundary indices that should be integrated over.

[DanielDoehring]

@Arpit-Babbar I took the liberty to push this a little further as I want to do some actual aerodynamic simulations which also involve lift (and especially drag) coefficients due to viscous forces.

For this, the coefficients due to pressure should be merged first.

[andrewwinters5000]

This is a very nice additional feature. Most of my comments / suggestions are related to notation and variable names.

[andrewwinters5000]

LGTM! Many thanks @Arpit-Babbar och @DanielDoehring this is a very nice feature to add to Trixi.