refactor: Improved use of type annotations, replace typing by t

[ArneGudermann]

Resolve the typing part of #958

[phorward]

Hello @ArneGudermann,
thanks for facing this big issue.

Since Python 3.9 and PEP-585, type annotations do not rely on the typing-module. Therefore, I would like to use this newer syntax consequently.

I would like to generally suggest the following changes:

• t.Dict replace by dict
• t.List replace by list
• t.Union replace by |

This also makes the import of typing pointless in most situations.
What does @sveneberth think about this suggestion?

[sveneberth]

I would like to generally suggest the following changes:

• t.Dict replace by dict
• t.List replace by list
• t.Union replace by |

Yes is good. Use everything that works as a generic, including tuple. In addition, it is then clear that it is prototypes.List and not typing.List.

We can thing also if we prefer str | None over t.Optional[str]. I think t.Optional also expresses that it is really just an argument / option that has to be used and passed if necessary. But technically, of course, it comes down to the same thing.

[phorward]

Yes is good. Use everything that works as a generic, including tuple. In addition, it is then clear that it is prototypes.List and not typing.List.

Err... should we now use my suggestion, or is typing.Dict, etc. better?

[phorward]

Hello @ArneGudermann, thanks for the update.
I really want to merge this quickly.

Can you please check in your code to use set[x] instead of t.Set[x] and to not import t in case it is not used?

Afterwards, we can merge this, to avoid huger merge conflicts in future, as this changes a lot of code.

[phorward]

@ArneGudermann please resolve current conflicts.
@sveneberth can you please file your review, too?