Add many geometrical quantities to ffcx expression generator.

[jorgensd]

Fix various errors in the definition of geometry tables

[coveralls]

coverage: 82.122% (+1.0%) from 81.168%
when pulling 8957b93 on dokken/expand-facet-expressions
into 3a6eb07 on main.

[jorgensd]

@michalhabera I've added tests that uses basix. Thus this checks that our expression generator handles the basix data correctly.

[michalhabera]

@michalhabera I've added tests that uses basix. Thus this checks that our expression generator handles the basix data correctly.

I think that your test logic is correct. We basix evaluates these we should not test against numerical values, but against what basix returns.

But can you unify naming there for translated names? E.g. reference_facet_jacobian -> facet_jacobians, so we translate UFL names to basix names. Currently there is additional naming scheme for which I do not see the point and system.

[jorgensd]

@michalhabera I've added tests that uses basix. Thus this checks that our expression generator handles the basix data correctly.

I think that your test logic is correct. We basix evaluates these we should not test against numerical values, but against what basix returns.

But can you unify naming there for translated names? E.g. reference_facet_jacobian -> facet_jacobians, so we translate UFL names to basix names. Currently there is additional naming scheme for which I do not see the point and system.

Done