We need to review cases where `Self` was unsupported, and thus we were using the (hardcoded) class name instead of `Self`.
Now the `Self` keyword is available in a almost or all contexts.
I have completely removed TypeAccessor.TranslateSelfType() method and related code:
From now on, `Self` is never translated to the actual type.
Note that Swift 5.1 still does not seem to accept `Self` in some contexts.
Example (from `ShouldConvertTypeofSelfToSelfWhenClassNameIsUnknown()` test, running on Xcode 11 beta 6):
I still found it better to never translate `Self` to the underlying class to simplify the converter code (since this did not add any new errors in the set of test projects).
If we find real-world cases when a variable declaration uses `typeof(self)` as a type name, let's revisit that.