Add a SpinerEosDependsRhoSie constructor that uses an existing eos object to generate a spiner eos

[buechlerm]

PR Summary

Much of this was generated by AI. I had asked it to emulate sesame2spiner in terms of parameters for grid generation. Seems somewhat heavyweight, but there are defaults. Ultimately, if somebody proposes a different way of parameterizing the grids, I'd accept that.

PR Checklist

• Adds a test for any bugs fixed. Adds tests for new features.
• Format your changes by using the make format command after configuring with cmake.
• Document any new features, update documentation for changes made.
• Make sure the copyright notice on any files you modified is up to date.
• After creating a pull request, note it in the CHANGELOG.md file.
• LANL employees: make sure tests pass both on the github CI and on the Darwin CI
• If ML was used, make sure to add a disclaimer at the top of a file indicating ML was used to assist in generating the file.
• If Agentic AI was used, have the AI generate a "proposed changes" markdown file and store it in the plan_histories folder, with a filename the same as the MR number.

If preparing for a new release, in addition please check the following:

• Update the version in cmake.
• Move the changes in the CHANGELOG.md file under a new header for the new release, and reset the categories.
• Maintainers: ensure spackages are up to date:
  • LANL-internal team, update XCAP spackages
  • Current maintainer of upstream spackages, submit MR to spack

[buechlerm]

Ok, this is effectively feature complete. I've made choices on what is the prefered path from an incomplete eos to the tables, but I'm not dead set on them, so if somebody has a very strong preference, I can change it. @adamdempsey90 was also working on some sesame2spiner changes and if he wants a different way of defining the table grids, I'm open to that as well. Finally, I said feature complete, but a future feature that is probably required is writing an sp5 file (for restarts at minimum). I'm putting that off till later.

[buechlerm]

There are actually a few more features we would want (I just don't need them for my Ristra work). Here, I punted on split-eos and mass fractions. We definitely want to optionally support those as well. Again, punting on those, till later, unless somebody sees something atrocious about this MR that'll make adding those features difficult, later.

[Yurlungur]

Thanks, @buechlerm this is really nice and it's functionality we've been missing for a long time. I have some review comments that entail varying amounts of work. Feel free to push back on them.

[buechlerm]

Took me some time, sorry, but I believe I've addressed comments.

[Yurlungur]

This looks great now. Thanks for the lift! A few nitpicks still, but I think they're non-blocking.

[Yurlungur]

@buechlerm is this ready to go? re-git indicates yes? if so, merge when ready