Move Several PostProcessors from RAVEN to SR2ML

[wangcj05]

---

Pull Request Description

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

close #1552
In order to move these PostProcessors to SR2ML, the PostProcessorReadyInterface class is created for temporarily handle the situation: some PostProcessors are using 'dict' as in and out operations, while others using 'xarray.Dataset' as in and out operations.
Most of the methods from PostProcessorPluginBase are moved to PostProcessorReadyInterface.

When all internal PostProcessors are converted to only use 'xarray.Dataset' as in and out operation. The class 'PostProcessorReadyInterface' and 'PostProcessorInterface' will be merged to form the new base class for all PostProcessors.

The corresponding PR in SR2ML is: idaholab/SR2ML#22

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

---

For Change Control Board: Change Request Review

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

• 1. Review all computer code.
• 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).
• 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
• 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.
• 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.
• 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.
• 7. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.
• 8. If an analytic test is changed/added is the the analytic documentation updated/added?
• 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.

[wangcj05]

@alfoa @mandd This PR is ready for you to review. Please also check PR: idaholab/SR2ML#22

[alfoa]

Only few comments

[alfoa]

@wangcj05 once merged, please send an email to the user list to inform that the CPRA/DPRA specific PP have been moved to SR2ML.

[alfoa]

Checklist passed (pending tests).

Approved...

Merging once tests pass.

[alfoa]

RrR in qsub failing @wangcj05

[moosebuild]

Job Test qsubs on f9566e9 : invalidated by @wangcj05

retest tests/framework/CodeInterfaceTests/RAVEN/ReturnDatabase

[alfoa]

Checklist passed .

Approved...

Merging...

[wangcj05]

@alfoa Qsub Test is green now. I have tested the failed test on my local machine, so far no failed case (63 in total, no failed case)