useful for remapping a mesh onto a (slightly modified) CAD, for sensitivity analyses

No commit message

In that case we search for all the matches in the octree, and we try to return amongst those the element that matches the input coordinates.

We use this in MathEval so we can reliably make operations on discontinuous datasets (e.g. edge element vector fields), on identical meshes that were possibly reordered.

Enforce volume positivity of 3D elements right after mesh generation/optimization, instead of enforcing when writing to file

Small simplifications + Preparation for Formulation Independent FS + Preparation for multiple Formulations using same FS

and Python onelab clients.

WARNING WARNING WARNING: This is a major change -- all our onelab-enabled .geo
and .pro files will need to be (slightly...) modified.

What's new:

1. The name of a onelab variable (in the onelab database) is no more constructed
   from the name of the corresponding GetDP/Gmsh variable. One now needs to
   specify the onelab name explicitely, using the "Name" attribute. The "Name"
   is the actual name of the parameter in the onelab database, i.e., it also
   includes the path.
   
   This makes the "Path" attribute obsolete (it has no effect anymore). The
   "Legend" attribute can still be used (and it can be useful in edge cases,
   e.g. when you want a "/" in the name of a onelab paramater), but in most
   cases it's not necessary.

2. When a DefineConstant[] & co is used and no Name is given
   (e.g. DefineConstant[a=2]), no onelab parameter is created. This allows to
   provide default values to internal parameters without polluting the database.

Why did we change?

1. The new syntax matches what we do in Python, where specifying a name is
   mandatory (there's no way around this in Python, as onelab cannot guess the
   name of a Python variable to which a onelab parameter value will be assigned).
   
   The change will prevent common mistakes where two parameters with the same
   label actually correspond to 2 different onelab parameters, due to a change
   in local getdp/gmsh variable name (which would change the onelab name
   automatically)

2. The new syntax allows to nicely decouple onelab parameters from internal
   variables with default values, that we don't want in the onelab database.

No commit message

dg : do not initialize dofContainer to 0 by default
dg : all testcases ported to python3
gmsh : use dcopy/zcopy in fullMatrix::setAll
gmsh : add a flag to prevent initialization of fullMatrix

 -- Using PView
 -- Removing Writer for FEMSolution and ElementSolution (layer for PView)
 -- Adapting System
 -- Interpolator simplified (left until PView can handel arbitrary basis)

** Mesh: new method
 -- Can access all the coordinates of the vertices
 -- Used by Interpolator

** Simulations: Huge Cleaning
 -- Intializing by SmallFem for all simulations
 -- Merging all Projections into on code
 -- Use of FEMSolutions and ElementSolutions
 -- Rewriting ShowFunctionSpace to use only FEMSolution
 -- Convergence Tests done again (see further)

** Assembler: Removing SystemShowFunctionSpace
 -- Done in Simulation

** FunctionSpace:
 -- Changing interface in BasisLagrange
 -- Cyclic permutations reactivated in ReferenceSpace (see further)

** WARNING: Without cyclic permutation TetEdgeBasis does NOT converge !!
 -- Works in 2D
 -- Works with TetNodalBasis
 -- Fails with TetEdgeBasis
 -- ShowFunctionSpace shows weird thing for some Tets
 -- Implementation or math error ????

** Convergence Tests WITH cyclic permutation
 -- Works everywhere (line, tri, quad, tet)