uxarray/utils/computing.py not used anywhere, and `pyfma` not in pyproject.toml

[Sevans711]

uxarray/utils/computing.py internally imports the pyfma package, which is not included in uxarray's dependencies, not even as an optional dependency, and it is also not being used anywhere else in uxarray, from what I can tell. Noticed this while working on #1575.

Additionally, none of the methods from uxarray/utils/computing.py are being used anywhere else in the entire uxarray codebase. I cannot tell why this module exists, from looking through the code.

Two possible solutions:

1. Remove the uxarray/utils/computing.py module.
2. Keep the module, but document why it exists, and handle pyfma package dependency appropriately.

• Documentation options include: add a docstring at the top of the file (see Improve code skimmability by adding docstring to tops of .py files #1598); write about it on readthedocs pages; and/or add at least one example to the docs pages which utilize it.
• Handling the dependency appropriately includes adding it as an optional dependency in pyproject.toml (see also: Refactor dependencies to make more optional #1548).

[Sevans711]

Realized I should probably ping @hongyuchen1030 on this one, as the person who implemented many (all?) of the methods in this module. Do you know if there are any imminent plans to incorporate uxarray/utils/computing.py functionality elsewhere in uxarray, or if it already being used downstream anywhere?

To clarify, I'm not trying to push towards removing this module, rather, I mostly just want to understand why it exists, and help that reason remain clear for anyone who looks into it in the future. I would only want to remove it if there really is no current/planned use case for it.

[hongyuchen1030]

Realized I should probably ping @hongyuchen1030 on this one, as the person who implemented many (all?) of the methods in this module. Do you know if there are any imminent plans to incorporate uxarray/utils/computing.py functionality elsewhere in uxarray, or if it already being used downstream anywhere?

To clarify, I'm not trying to push towards removing this module, rather, I mostly just want to understand why it exists, and help that reason remain clear for anyone who looks into it in the future. I would only want to remove it if there really is no current/planned use case for it.

This has already been addressed in #1513. uxarray/utils/computing.py shouldn't be removed, since it serves as the main algorithmic highlight of UXarray, providing the EFT-based floating-point operators. @rajeeja has already cleaned it up in #1513, so no further action is needed here before this branch is merged.

For context: this module predates Python's support for the FMA instruction, and at the time we weren't able to find a suitable substitute. We've since dropped our dependence on it, but an actual cleanup pass after #1513 merges is definitely recommended.