Together with the new test, this commit also contains a number
of fixes for the SurfaceCosseratEnergy class.  This class was
not unit-tested previously, and unintentionally I messed it up
badly during my recent modernization work.

Finally, SurfaceCosseratEnergy had apparently never been tested
without dune-curvedgeometry, which is however only an optional
dependency.  The commit therefore also adds the necessary
conditionals.

Then problem then is that the derivative of the outer normal
of an intersection is not available from the standard grid interface.
If dune-curvedgeometry is not available, this derivative is
simply set to a zero matrix.  Depending on the grid manager
this may not actually be correct, though.

Various cleanup patches

See merge request !143

CollectiveCommunication has been deprecated for a while, and has
recently been removed from dune-grid.

'thickness' and 'kappa' are parameters in Cosserat shell models.
They are not necessary for bulk models.  Hence remove them.

They do the same thing, essentially.

This is what the non-mixed ADOL-C assembler does, and I want to
merge the two.

Both classes are meant to do the same thing.

This makes the interface more consistent.

These two exist in base classes, and they are inherited anyway.

ADOL-C can compute all derivatives with two different modes:
scalar- and vector mode.  In theory they should produce exactly
the same results, but sometimes there are bugs (I have found
a few of those myself).  adolctest-scalar-and-vector-mode tested
whether the two modes produced the same result for a particular
Cosserat configuration.

I do not think that dune-gfe is the right place for such a test.
It tests for bugs in ADOL-C itself, and that is the job of
ADOL-C's own test suite.  Consequently, I am removing the test.

This allows to get rid of a lot of (all) multiple inheritance.

Previously, LocalEnergy would accept an arbitrary number of
template arguments, and (with the exception of the first one)
they would be interpreted as the factors of a product target space.
This patch replaces this template list by a single template
parameter, which has to be ProductManifold if a product space
is desired.

This has implications throughout the code.  In particular, there are
now two energy methods: One that still accepts coefficients sets
in the form

  std::vector<TargetSpace>

and a second one which accepts

  TupleVector<std::vector<Factors>...>

The second one really only makes sense for product manifolds.
However, as the 'energy' methods are pure virtual, they cannot be
disabled by SFINAE or C++20 concepts.  Therefore, the second 'energy'
method exists always, accepting

  TupleVector<std::vector<TargetSpace> >

if TargetSpace is not a product.

In the long run this is cleaner than setting up the type in
the LocalStiffness class itself.

This will later simplify merging the mixed and non-mixed versions
of the assembler code.

The rest of the HarmonicEnergy class is now independent of
the density.  It is functionally equivalent to the LocalIntegralEnergy
class, and shall be replaced by that eventually.  However,
LocalIntegralEnergy still has the deformation/rotation-split
hard-coded in a few places, and that needs more work.

The new method is Fufem::markBoundaryPatchDofs, which apparently
works in just the same way.

Currently, Cosserat materials are hard-wired in the interface.
This patch changes the interface a little bit towards being
more general.

That's another step closer towards merging the
MixedLocalGeodesicFEStiffness and the LocalGeodesicFEStiffness.
Also, it is necessary to be later able to generalize the code
for product spaces with more than two factors.

It is deprecated, and not used anymore.

... rather than two separate spaces.  This is one step towards
getting rid of it altogether.

... regarding ambiguous logical expressions.

Update instrumented path for Riemannian TR and PN solvers.

See merge request !142

Replace RigidBodyMotion by ProductManifold

See merge request !141

The ProductManifold class generalizes RigidBodyMotion, and can do
everything that the RigidBodyMotion class can.  Therefore there is
no point in keeping RigidBodyMotion any longer.  Having two
implementations for the same thing will just confuse people.

It contained code for mixed-dimensional domain decomposition algorithms
involving Cosserat materials.  This code has moved to a separate modul
'dune-gfe-coupling' a long time ago, and it is not used from anywhere
else in dune-gfe.

Add a CI job that runs uncrustify and checks for modifications

See merge request !140