(after recent changes to editor painting code)

Fixes IDEA-93038 Inspection: Replace Collections.sort() with Arrays.sort()

Fixes EA-115791 - IOE: PsiJavaParserFacadeImpl.createExpressionFromText

Vitaly Provodin

For that I introduced a new method -- getElement() in PyType
that allows to find out the element that can be used to reference
this type according to PEP 484 perspective, e.g. a target assignment
for TypeVar's and NamedTuples and PSI class themselves for class types.

Also, class object types for named tuples are wrapped in typing.Type[]
as expected.

by adding an alternative implementation of TypeVisitor that strives
to render a type in PEP 484 compatible format.

Also PyCollectionType now properly implements PyClassType since
both of it inheritors: PyCollectionTypeImpl and PyTupleType already
extend PyClassTypeImpl.

I had to separate PyTypeVisitor into two abstract classes since
(quite confusingly) not all types of our type system are available in
python-psi-api module.

Now it's possible to distinguish between them when both are offered
on a target of a call expression result assignment (as it was noticed
during the testing of PY-16412).

Namely, it was mistakenly dereferenced before the document was
committed after modifications.

Callable types are still not rendered properly in PEP 484 compatible
format, but at least they don't lead to PIEAE anymore.

since they cannot be expression in PEP 484 compatible format (yet).