runTimePostProcessing: use existing cutting planes

Cross ref : EP#868

@andy @mark

mentioned in issue #1125 (closed)

mentioned in commit 7843015075cf24742805c9a13d16b6dd79c9b922

mentioned in commit 0cbb07f5db4431e3ad8a17525cfbef82c6deecd7

mentioned in issue #1126

Add direct support for vtp surfaces

mentioned in commit 98fb25e7bcb8476c92cd5cb17f7a95bb1e63784f

@Prashant - This should now handle vtp properly for current and future. I tested (ellipse tutorial) using surfaceMeshTriangulate to extract the boundary surface.

Another point for checking is the dummy runTimePostProcessing. If you have a system without VTK or ParaView for compilation, it should now create a stub for the functionObject. If you use runTimePP and don't have the proper VTK libs at compile time, it should now just complaint and toss out the function object, but not crash anything.

With possibility of creating image during the run, this development is no longer required.

We can revisit if someone is interested again in future.

closed