Prepare setting up polyhedron from both Vrep and Hrep for different backends

[kliem]

#22701 implemented setting up a polyhedron from both Vrep and Hrep for the backend field.

There are plans to allow the same for polymake #26368 and with #28639 at hand we can do the same for normaliz.

So it makes sense to set up a general framework for initializing from Vrep and Hrep. This ticket does this (or rather moves what was done in #22701 accordingly).

If a backend implements the method _init_from_Vrepresentation_and_Hrepresentation, then the initialization of Polyhedron_base may use it if Vrep_minimal and Hrep_minimal is both set to true.

This option will not be exposed in the function Polyhedron, as a user should really know what they are doing.

Also the method _element_constructor_polyhedron of Polyhedra_base sets up the new polyhedron from both representations, if self.Element has the method _init_from_Vrepresentation_and_Hrepresentation.

CC: @jplab @LaisRast

Component: geometry

Keywords: polytopes, backend, Vrep, Hrep, initialization

Author: Jonathan Kliem

Branch/Commit: 561a629

Reviewer: Jean-Philippe Labbé

Issue created by migration from https://trac.sagemath.org/ticket/28880

[kliem]

Commit: ffcc0bd

[kliem]

Branch: public/28880

[kliem]

New commits:

ffcc0bd

prepare setting up from both Vrep and Hrep in general

[sagetrac-git]

Changed commit from ffcc0bd to 2c9321e

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

2c9321e

removed unused import

[embray]

comment:3

Ticket retargeted after milestone closed

[kliem]

New commits:

cb91aa5	prepare setting up from both Vrep and Hrep in general
cc8765a	removed unused import
561a629	fixed pyflakes warning

[kliem]

Changed commit from 2c9321e to 561a629