Test production against changes to upstream packages

[MTCam]

This PR is here just to test current production/prediction code against any changes to upstream packages.

To prepare and run the tests:

0. Check the CEESD forks of (grudge, meshmode, arraycontext, pytato, and loopy) to see if they lag behind the inducer@main versions (update the CEESD forks if they lag).
1. Check out illinois-ceesd/pkg@production-pilot for any updated packages and merge the (now updated) illinois-ceesd/pkg@main changes and push
2. Ensure this mirgecom@production-pilot branch is updated with mirgecom@production and push or otherwise kick CI.

If all of these tests pass, then illinois-ceesd/pkg@production-pilot can be safely merged into illinois-ceesd/pkg@production

Questions for the review:

• Is the scope and purpose of the PR clear?
  • The PR should have a description.
  • The PR should have a guide if needed (e.g., an ordering).
• Is every top-level method and class documented? Are things that should be documented actually so?
• Is the interface understandable? (I.e. can someone figure out what stuff does?) Is it well-defined?
• Does the implementation do what the docstring claims?
• Is everything that is implemented covered by tests?
• Do you see any immediate risks or performance disadvantages with the design? Example: what do interface normals attach to?