Tally segment parsing bug fix.

[MicahGale]

Description

This fixes a parsing error with tally segments that have an end t.

Fixes #377

Checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation (if applicable)
• I have added tests that prove my fix is effective or that my feature works (if applicable)

[coveralls]

Pull Request Test Coverage Report for Build 9492465919

Details

• 14 of 14 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.005%) to 98.228%

---

Totals
Change from base Build 9490293834:	0.005%
Covered Lines:	5764
Relevant Lines:	5868

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 9492487926

Details

• 14 of 14 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.005%) to 98.228%

---

Totals
Change from base Build 9490293834:	0.005%
Covered Lines:	5764
Relevant Lines:	5868

---

💛 - Coveralls

[tjlaboss]

Testing with C:

>>> import montepy
>>> dblock = montepy.input_parser.mcnp_input.Input(["fs567 -1 -2 t c"], montepy.input_parser.block_type.BlockType.DATA)
>>> montepy.data_inputs.data_parser.parse_data(dblock)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "MontePy/montepy/data_inputs/data_parser.py", line 53, in parse_data
    return data_class(input)
  File "MontePy/montepy/data_inputs/data_input.py", line 54, in __init__
    super().__init__(input, self._parser)
  File "MontePy/montepy/mcnp_object.py", line 57, in __init__
    raise ParsingError(
montepy.errors.ParsingError:     , line 0

    >    0| fs567 -1 -2 t c
          |               ^ not expected here.
There was an error parsing "c".
sly: Syntax error at line 1, token=TEXT

[MicahGale]

Testing with C:

>>> import montepy
>>> dblock = montepy.input_parser.mcnp_input.Input(["fs567 -1 -2 t c"], montepy.input_parser.block_type.BlockType.DATA)
>>> montepy.data_inputs.data_parser.parse_data(dblock)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "MontePy/montepy/data_inputs/data_parser.py", line 53, in parse_data
    return data_class(input)
  File "MontePy/montepy/data_inputs/data_input.py", line 54, in __init__
    super().__init__(input, self._parser)
  File "MontePy/montepy/mcnp_object.py", line 57, in __init__
    raise ParsingError(
montepy.errors.ParsingError:     , line 0

    >    0| fs567 -1 -2 t c
          |               ^ not expected here.
There was an error parsing "c".
sly: Syntax error at line 1, token=TEXT

This is what I get for trying to close a bug without reading or understanding the FS documentation. Of course they made c a keyword.

[coveralls]

Pull Request Test Coverage Report for Build 9550870299

Details

• 14 of 14 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 98.245%

---

Totals
Change from base Build 9550865708:	0.02%
Covered Lines:	5765
Relevant Lines:	5868

---

💛 - Coveralls

[tjlaboss]

New test covers the 'c for cumulative' syntax, and MontePy now correctly parses it.