Improving the flexibility of the shuffling logic

[jasonbmeng]

What is the change? Why is it being made?

These changes enable different ARMI applications to share a common shuffling input definition utilizing ring & position at cycle instead of assemblyName. This is particularly useful for movements where an assembly which has been discharged from the core (e.g. to the spent fuel pool) needs to be reintroduced into the core in a later cycle of operation.

Currently, the input format to specify an assembly moving from the spent fuel pool back into the core uses the assemblyName. However, assemblyName (i.e. assembly number) is not guaranteed to be consistent across ARMI Apps. For example, one App may run a full core model while another leverages core symmetry and models a 1/3 symmetric core model. Both applications should be able to interrogate a common shuffling definition and parse consistent assembly movements.

This PR moves spent fuel pool assembly identification away from using the assemblyName. Instead, the assembly location history is used. The input is now ring, position, and cycle. This is used to identify the target assembly which resided at (ring, position) during cycle.

SCR Information

Change Type: features

One-Sentence Rationale: Different ARMI Applications should be able to share common shuffling input definitions which are independent of application specifics such as assembly numbering.

One-line Impact on Requirements: N/A, this seems to fall under requirement R_ARMI_SHUFFLE with new testing covered under T_ARMI_SHUFFLE

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify any new/changed code.
• The documentation is still up-to-date in the doc folder.
• The code style follows good practices.
• The dependencies are still up-to-date in pyproject.toml.