remove Octavian and matmul!

[jlchan]

Would address #1906, and is the first step in addressing #1789.

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.15%. Comparing base (887bab9) to head (9a567d7).

Additional details and impacted files

@@               Coverage Diff               @@
##           jc/dev_DGMulti    #1950   +/-   ##
===============================================
  Coverage           96.15%   96.15%           
===============================================
  Files                 454      454           
  Lines               36509    36509           
===============================================
+ Hits                35102    35103    +1     
+ Misses               1407     1406    -1     

Flag	Coverage Δ
unittests	96.15% <100.00%> (+<0.01%)	⬆️

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.

[jlchan]

@ranocha @JoshuaLampert I requested your reviews since you both commented on #1789. I am planning on merging PRs associated with this in a staging branch, and thought this might make it easier to review than a single large PR.

Let me know if you'd prefer to proceed otherwise

[jlchan]

Is the MPI-macos test failure due to the Codecov issue when the PR is from a fork of the repo?

[ranocha]

Is the MPI-macos test failure due to the Codecov issue when the PR is from a fork of the repo?

Yes, exactly. It would be easier if you could make the PRs from branches in the main repo

[ranocha]

Seems fine as a first step. Thanks

[JoshuaLampert]

Thanks for taking care of this @jlchan!