Ingesting tabulate as an internal module

[john-science]

What is the change?

I removed the tabulate dependency, and just ingested the parts of that tool we use to armi.utils.tabulate.

Why is the change being made?

To close #1749

The problem is that tabulate appears to be a nigh abandoned project, and it is keeping us from being able to support modern PIP versions.

(Arrielle also points out that we could just replace tabulate with something else, like prettytable. I am not super convinced my approach here is better than that one. I went this route first because it was easy for me to do, and would be easier to make the update for our downstream repos.)

Code Coverage

The code coverage on this file is pretty high:

---

Checklist

• This PR has only one purpose or idea.
• 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.

[jakehader]

I think it's fine to pull in 🐫 case throughout and then move code over to armi's tabulate as it makes sense. Should be pretty easy to see where to replace these things. Could also replace things that are 🐍 case with a simple name (tabular_data -> data or something). Should we pull in additional documentation of this new feature into the ARMI docs? For example pull in examples from https://github.com/astanin/python-tabulate?tab=readme-ov-file#library-usage?

[john-science]

I think it's fine to pull in 🐫 case throughout and then move code over to armi's tabulate as it makes sense. Should be pretty easy to see where to replace these things. Could also replace things that are 🐍 case with a simple name (tabular_data -> data or something). Should we pull in additional documentation of this new feature into the ARMI docs? For example pull in examples from https://github.com/astanin/python-tabulate?tab=readme-ov-file#library-usage?

Most of that is already included in the docstring for the tabulate.tabulate() function:

armi/armi/utils/tabulate.py

Lines 1027 to 1043 in cac3324

	r"""Format a fixed width table for pretty printing.
	>>> print(tabulate([[1, 2.34], [-56, "8.999"], ["2", "10001"]]))
	--- ---------
	1 2.34
	-56 8.999
	2 10001
	--- ---------
	The first required argument (`data`) can be a list-of-lists (or another iterable of
	iterables), a list of named tuples, a dictionary of iterables, an iterable of dictionaries, an
	iterable of dataclasses (Python 3.7+), a two-dimensional NumPy array, or NumPy record array.
	Table headers
	-------------
	To print nice column headers, supply the second argument (`headers`):

I considered putting what you linked as a module-level docstring, and reducing this ridiculously long function docstring (>200 lines). I could do that, and find any missing pieces from the docs you linked as well.

[opotowsky]

We are waiting to merge, but in the meantime: approved! tabulate is officially pac-manned!

[john-science]

@jakehader I grabbed that README and put it in the module-level docstring in this file. Thanks!