Petascope_Use axis's positions in CRS definitions instead of axis labels

[Bang Pham Huu]

Currently, WCST_Import and Petascope use axis labels from CRS Definitions (e.g: Lat, Long in EPSG/0/4326). However, with CIS 1.1 and the change from SECORE (EPSG version 0 points to the latest EPSG version inside SECORE). The axis labels are not reliable anymore (e.g: for EPSG 4326 'Long' → 'Lon').

The problem is in Petascope it also relies on axis labels to detect axis type (X, Y), e.g:

// List of case-sensitive EPSG aliases of axis abbreviation of the same type (grouped in petascope.util.AxisTypes interface)
    // src: http://www.epsg-registry.org/
    public static final List<String> X_ALIASES = Arrays.asList(
                "X",    // eg CS EPSG:6507 \
                "E",    // eg CS EPSG:4400  |
                "M",    // eg CS EPSG:1024  |- CARTESIAN CS
                "E(X)", // eg CS EPSG:4496  |
                "x",    // eg CS EPSG:4531  |
                "e",    // eg CS EPSG:6504 /
                "Long", // eg CS EPSG:6422 ELLISPOIDAL CS
                "Lon",  // eg PS:1 (gdalsrsinfo)
                "i"     // eg ImageCRS
            );
    public static final List<String> Y_ALIASES = Arrays.asList(
                "Y",    // eg CS EPSG:6507 \
                "N",    // eg CS EPSG:4400  |
                "P",    // eg CS EPSG:1024  |- CARTESIAN CS
                "E(Y)", // eg CS EPSG:4496  |
                "y",    // eg CS EPSG:4531  |
                "n",    // eg CS EPSG:6504 /
                "Lat",  // eg CS EPSG:6422 ELLISPOIDAL CS
                "j"     // eg ImageCRS
            );

So the problem is to find a way to detect axis types (X, Y) properly first.