Does not make use of typeapi's ability to evaluate future Type hint syntax in Python 3.8

[NiklasRosenstein]

Example traceback:

 File "/home/coder/.dotfiles-reconciler/venv/lib/python3.8/site-packages/databind/json/converters.py", line 418, in _get_schema
    return self.convert_to_schema(datatype)
  File "/home/coder/.dotfiles-reconciler/venv/lib/python3.8/site-packages/databind/core/schema.py", line 128, in convert_to_schema
    schema = convert_dataclass_to_schema(hint.type)
  File "/home/coder/.dotfiles-reconciler/venv/lib/python3.8/site-packages/databind/core/schema.py", line 189, in convert_dataclass_to_schema
    annotations = get_annotations(base_type)
  File "/home/coder/.dotfiles-reconciler/venv/lib/python3.8/site-packages/typeapi/utils.py", line 321, in get_annotations
    annotations = _get_type_hints(obj, globalns=globalns, localns=localns)
  File "/usr/lib/python3.8/typing.py", line 1232, in get_type_hints
    value = _eval_type(value, base_globals, localns)
  File "/usr/lib/python3.8/typing.py", line 270, in _eval_type
    return t._evaluate(globalns, localns)
  File "/usr/lib/python3.8/typing.py", line 518, in _evaluate
    eval(self.__forward_code__, globalns, localns),
  File "<string>", line 1, in <module>
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'

Seems like we end up evaluating the annotations inside of typeapi.get_annotations() without the future support.

[NiklasRosenstein]

This might as well be a bug in typeapi.