Add combined nonconservative GPU volume and boundary condition kernels

[MarcoArtiano]

The callback for the divergence is broken on the GPU, because we pass the full cache on the GPU, which is not filtering to not contain not-bitstype. I just avoided having these callbacks in the tests when running on the GPU by changing the analysis_callback.

Some additional notes: the volume kernel implemented only works if the volume flux is implemented following the combine_conservative_and_nonconservative_fluxes. The boundary conditions instead are for the moment only for the original implementation of the nonconservative terms. To summarize, nonconservative systems on GPU now runs only if the volume flux is passed as combine_conservative_and_nonconservative_fluxes and the surface flux is passed as surface_flux = (flux_conservative, flux_nonconservative).

Note that the calc_interface_flux! already provides the flexibility to run with plain original implementation and combined option for nonconservative systems on the GPU.

[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 with its PR number.

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.