User source terms

[adamdempsey90]

Background

This adds a simple mechanism for enrolling "user" source tasks into the driver. Disk wave-killing was added as an example.

This supersedes #114

Description of Changes

Checklist

• New features are documented
• Tests added for bug fixes and new features
• (@lanl.gov employees) Update copyright on changed files
• Any contribution that was created or modified with the assistance of generative AI must have a comment disclosing this such as // This file was created in part or in whole by generative AI

[adamdempsey90]

I didn't know you could pass names to tasks

[pdmullen]

Should the enrollment function name reflect that this is an "unsplit" source term enveloped in the temporal integrator logic --- that is, NOT an operator split source term enrolled after an e.g., rk2 advance?

[adamdempsey90]

Should the enrollment function name reflect that this is an "unsplit" source term enveloped in the temporal integrator logic --- that is, NOT an operator split source term enrolled after an e.g., rk2 advance?

I think that clarification is good if we have more than one type of user source term, but if we only have one, then it should be clear from the documentation what it's for (the current documentation is not clear / non-existent).

I could just add a few of these registries for the different flavors (explicit, implicit, operator-split, etc.)

[adamdempsey90]

Should the enrollment function name reflect that this is an "unsplit" source term enveloped in the temporal integrator logic --- that is, NOT an operator split source term enrolled after an e.g., rk2 advance?

I think that clarification is good if we have more than one type of user source term, but if we only have one, then it should be clear from the documentation what it's for (the current documentation is not clear / non-existent).

I could just add a few of these registries for the different flavors (explicit, implicit, operator-split, etc.)

I added 3 collections, 1 for explicit unsplit tasks, 1 for implicit unsplit tasks ("implicit" in the IMEX sense in terms of ordering), and 1 for split task lists.