Constructor with
DataType& dataNavierStokes
does not need
GetPot&   data_file,

NavierStokesAleHandler:
definting _dw etc...

* choose pattern according to solver/matrix type
* renamed and reorganized element matrices to have more understandable names

* add constructor from a CSR pattern object
* add some documentation

* use z1 = ZeroVector( dim ) for setting vector z1 to zero

* call AZ_free_memory where appropriate
* copy rhs instead of const cast (cleaner, but less efficient)

Note: fluxes calculated before this bugfix may be wrong, as memory for x
      component of normal was "shared" with someone else...

1.- simple use: first add variables and then call postProcess( time )
2.- makes uses of the ensight case file
3.- handles the case of moving domains

Note: the interface could be used as an abstract class for post-processing

petsc is not really used anyway in the version of lifev
this is a test to see if petsc and related libs could be the culprits
it shall be reverted once the link/failure between lifev and  ( petsc and related libs ) is understood