Remove unused parameters related to reactivity coefficients

[keckler]

What is the change?

This PR is a big housecleaning of a bunch of parameters that were related to our old internal implementation of reactivity coefficient calculations. They are not used anywhere. I have run our internal integration tests and found no issues.

Why is the change being made?

These parameters are unused bloat. They should have been removed a long time ago. Many of them are ambiguous. Having these around makes working with parameters programmatically difficult.

Side note: These parameters would more properly belong in a plugin, since they are very specific and not used by multiple plugins.

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify that the new/changed code works.

• The code style follows good practices.
• The commit message(s) follow good practices.

• The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.
• The documentation is still up-to-date in the doc folder.
• No requirements were altered.
• The dependencies are still up-to-date in pyproject.toml.

[keckler]

@john-science We should talk about this in person tomorrow, if you have some time.

[john-science]

Chris and I have reviewed this.

This PR is tacitly approved, based on some testing Chris is running.

But also, I'm not going to hit "Approve" here until after the testing is complete (~24 hours), because I don't want someone YOLO-merging this PR just yet.

[keckler]

@john-science My internal testing came back clean. This consisted of running our integration tests and also a benchmark case that exercises this part of the code.

[john-science]

Test coverage only went down because we removed lines of code.

That is exceptable.

[keckler]

Thanks @john-science . I can coordinate the merge, since there are a few internal repos that will be merged simultaneously.

[keckler]

It was pointed out to me by @mgjarrett that I shouldn't remove rxFuelAxialExpansionPerPercent because it is planned to be used very soon by an internal plugin. Does it belong in that plugin instead of the framework? 😏