refactor: use native types over `typing` and remove `eval`s

[jkowalleck]

that the f...

eval of List[FooBar]( ... ) instead of native list(...) ...
the typing has no value here, this is pure runtime! and it is not only unnecessary overhead.

is this really needed?

and the FooBar is not even imported in this context, the typing just makes no sense !!!1elf

        _ARRAY_TYPES = {'List': List, 'Set': Set, 'SortedSet': Set}
        _DEFAULT_XML_SEQUENCE = 100
        _SORTED_CONTAINERS_TYPES = {'SortedList': List, 'SortedSet': Set}


# ...

                            # Will load any class already loaded assuming fully qualified name
                            self._type_ = eval(f'{mapped_array_type}[{results.get("array_of")}]')
                            self._concrete_type = eval(str(results.get("array_of")))

[Siddhesh-Agarwal]

We can use list instead of typing.List for Python >= 3.10 but this library supports Python >= 3.7. so we cannot use list directly, but I believe the FooBar can be removed for good.