Redesign of the constructor for Hyperelliptic curves

[anna-somoza]

As discussed in #22173, the current the design of the hyperelliptic curves classes was not good.

This changes create the (genus, ring) subclasses dynamically, removing the need for a class/file per case.

CC: @JRSijsling @mstreng @videlec @slel

Component: number theory

Keywords: days98, hyperelliptic curves

Author: Anna Somoza

Branch/Commit: fe002eb

Reviewer: Vincent Delecroix

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

[anna-somoza]

Branch: u/annasomoza/redesign_of_the_constructor_for_hyperelliptic_curves

[anna-somoza]

Author: Anna Somoza

[anna-somoza]

Description changed:

--- 
+++ 
@@ -1 +1,3 @@
+As discussed in #22173, the current the design of the hyperelliptic curves classes was not good.
 
+This changes create the (genus, ring) subclasses dinamically, removing the need for a class/file per case.

[anna-somoza]

Changed keywords from none to days98, hyperelliptic curves

[anna-somoza]

Commit: e4d5db4

[videlec]

Reviewer: Vincent Delecroix

[videlec]

comment:3

This is a good move.

The logic in the following is weird

fld = map(lambda fnc : fnc(R), [is_FiniteField, is_RationalField, is_pAdicField])
fld_type = fld.index(True)

You would rather do something like

fields = [
   ("FiniteField", is_FiniteField, HyperellipticCurve_finite_field),
   ("RationalField", is_RationalField, HyperellipticCurve_rational_field),
   ("pAdicField", is_pAdicField, HyperellipticCurve_padic_field)]
for name, test, cls in fields:
    if test(R):
        ....    # treat the class
        break   # the tests are exclusive, no need to run through all cases

[sagetrac-git]

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

1c35da7

Modify field-related data treatment