Serpent Interface Upgrade

[alfoa]

---

Pull Request Description

What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)

Closes #2289

What are the significant changes in functionality due to this change request?

This merge request is aimed to upgrade and make the SERPENT interface fully functional and flexible.

• Addition of support for eigen/criticality calculations (not only burnup)
• Usage of open source tool (serpentTools: https://serpent-tools.readthedocs.io/en/master/index.html) to parse results from serpent. The serpentTools library is not installed if a user does not invoke the serpent interface.
• Utility Function to create RAVEN variable groups has been rewritten to leverage Serpent output parser directly (if a modification of the parser is performed, the script is able to get it directly)
• Addition of embedded reactivity calculation
• Support of multiple output files (Result files, Detector outputs, Depletion outputs, Micro XS reader)
• Bumat support has been disabled since Serpent is removing (deprecated) such output format and all the info are already contained in the Depletion output (*dep.m format)
• Consistency checks in the input files (if an output is requested, the flags in the input are checked accordingly)

---

For Change Control Board: Change Request Review

The following review must be completed by an authorized member of the Change Control Board.

• [x] 1. Review all computer code.
• [x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
• [x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
• [x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
• [x] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options. Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in XML block, the node <internalParallel> to True.
• [x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change. The requirements and the requirements test shall be in sync.
• [x] 7. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.
• [x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
• [x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

[moosebuild]

Job Test qsubs sawtooth on a5b2cd7 : invalidated by @wangcj05

very slow in removing packages

[moosebuild]

Job Test qsubs sawtooth on a5b2cd7 : invalidated by @wangcj05

library issue

[wangcj05]

checklist passed. PR can be merged.

[alfoa]

@wangcj05 Thanks a lot!!!