Fix Enum ARRAY-mapping for extended classes.

[signedav]

Fix that colums of tables of extended classes cannot consider meta attributes, because they are stored according to the iliname - and an attribute of the base class that is used in a table of an extended class has still the iliname of the base class - thats why it now checks its real iliname instead of concatinating it from the tables iliname.

The example illuminates it:

MODEL BagOfEnumBase(en) AT "https://modelbaker.ch" VERSION "2023-03-29" =
  [...]
    CLASS Strasse =
        Name : MANDATORY TEXT*99;
        !!@ili2db.mapping=ARRAY
        Mat : BAG {1..*} OF BagOfEnumBase.Material_;
        Geometrie : MANDATORY BagOfEnumBase.CHLine;
    END Strasse;

And then extend it:

MODEL BagOfEnumExt (en) AT "https://modelbaker.ch" VERSION "2023-03-29" =
  IMPORTS BagOfEnumBase;
     [...]
    CLASS Strasse (EXTENDED)=
        Bemerkung: TEXT;
    END Strasse; 

(or with extra meta attribute file - like in the tests)

Before it created the table from the extended strasse. There it checked "BagOfEnumExt.Strassen.Strasse.Mat" for the entry in the t_ili2db_meta_attr table. But this was wrong. There is no ili-element like this. Mat is definitely an element of BagOfEnumBase.

With the new way of getting the ilielement it's much more stable and fixes this issue.

[gacarrillor]

@signedav, is there something critical with the test failures?

[signedav]

I think I have to fix it.

[signedav]

The query is correct, but the other tests were no longer correct. They were not tackled by the malfunction before, but checked the "wrong" values though