Updates for pin-related functionality

[albeanth]

What is the change?

These changes are to support upgrades in pin-related functionality. The changes in this PR can be lumped into the following buckets:

1. History Tracker: "detail assemblies" are now fuel and control assemblies. I also added some type hints to this module to help understand what was getting passed around.
2. Removing blocks.py::Block::breakFuelComponentsIntoIndividuals. This is removed because it is a very memory expensive way of storing pin level characteristics. Storing data as numpy arrays is much more manageable.
3. Move getPuMoles from blocks.py up to composites.py
4. Populate molesHmBOL and puFrac on components during completeInitialLoading.
5. Add a method getPinMgFluxes to retrieve the pin-wise multigroup fluxes from a Block.

Why is the change being made?

To support downstream pin-related functionality upgrades.

close #791

---

Checklist

• This PR has only one purpose or idea. Sorry 😞
• Tests have been added/updated to verify any new/changed code.

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

• The release notes have been updated if necessary.
• The documentation is still up-to-date in the doc folder.
• The dependencies are still up-to-date in pyproject.toml.

[albeanth]

@zachmprince a heads up

[john-science]

@albeanth This PR needs several release notes:

num	Your Change	Release Note
1	History Tracker: "detail assemblies" are now fuel and control assemblies.	Add this to "API Changes"
2	Removing breakFuelComponentsIntoIndividuals	Add this to "API Changes"
3	Move getPuMoles from blocks.py up to composites.py	Add this to "API Changes"
4	Populate molesHmBOL and puFrac on components during completeInitialLoading	ignore
5	Add a method getPinMgFluxes to retrieve the pin-wise multigroup fluxes from a Block.	Add to "New Features"

[drewj-tp]

Changes seem to be in order. Requesting release notes according to @john-science comment - #1990 (comment)

Some softer, non-blocking changes that I'd consider good to haves but not strictly needed at this time.

[drewj-tp]

If the parameter param is not defined on the parent, or is None, there could be a not great exception raised here. I would recommend some error helping, maybe a try/except/raise pattern like

try:
    return self.parent.p.get(param)[indexMap]
except Exception as ee:
    msg = f"Failure getting {param} from {self} via parent {self.parent}"
    runLog.error(msg)
    runLog.error(ee)
    raise ValueError(msg) from ee

or just allowing the raised exception to pass up, replacing the raise ValueError(msg) from ee with raise

[jakehader]

Did we check with the users of this to ensure that this doesn't need to be configurable? Specifically for pin performance evaluations? @sammiller11235?

[albeanth]

Yes. We were told that, for now, we are only concerned with fuel and control assemblies.

[onufer]

prior to this we only got fuel.

[drewj-tp]

Changes from @zachmprince look good. Just need release notes and I feel okay with this PR