Constraints parameter classes are basically just grid functions returning
bools. Going through interpolate.py reduces lots of reduntant code.

Working:
- Driver block
- Solving and visualization

Not working:
- Error calculation

These methods are part of the driver block class interface and should also be
generated if they are not used from the main function.

[ ] Go through system part -> GFS
[ ] Export boundary grid function

A pattern that we have been manually implementing in quite some places!

This is not used anymore since we have mixins.

In the /sumfact_poisson_dg_3d_unstructured_deg2_symdiff_nonquadvec_gradvec
test case this reduces the time spent in evaluation of it from >100s to 6s.

IT is both simplicial and quadrilateral...

So far, we were a bit sloppy about which basis we choose from the UFL
counterpart. This commit implements the necessary 1-to-1 mapping.

In many places we treat this as codegen-time information anyway.
For loopy, this is the necessary way to go.