Revert "Avoid deprecation warnings on GPU CI for now"

[vchuravy]

Reverts #3001

fixes #3002, closes #3005

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

[JoshuaLampert]

Since CUDA.jl did not release a new version yet since they fixed the deprecations from GPUCompiler.jl in JuliaGPU/CUDA.jl#3131, do we get the deprecation warnings again if we merge this PR and #2925 until they release a new version?

[JoshuaLampert]

Ok yes, CUDA tests fail again because CUDA.jl did not yet release a new version of CUDACore.jl after fixing the deprecation warnings in JuliaGPU/CUDA.jl#3131 (which is already one month ago).

[ranocha]

@vchuravy When will there be a new release of CUDACore.jl?

[JoshuaLampert]

A new release of CUDACore.jl is out, but to test it we need to wait until GPU tests are running again (ref https://discourse.julialang.org/t/psa-all-ci-services-temporarily-halted/137559).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.89%. Comparing base (7091f3b) to head (c524dd6).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3029   +/-   ##
=======================================
  Coverage   96.89%   96.89%           
=======================================
  Files         647      647           
  Lines       50021    50021           
=======================================
  Hits        48463    48463           
  Misses       1558     1558           

Flag	Coverage Δ
unittests	96.89% <ø> (ø)

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

☔ View full report in Codecov by Harness.
📢 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.

[JoshuaLampert]

LGTM!