Improve UX by using fully-qualified name in some `TypeError`

Feature or enhancement

Proposal:

The error message TypeError: Can't instantiate abstract class FOO without an implementation for abstract methods 'BAR' doesn't tell me with module FOO comes from.

This is unfortunate, particularly in larger code bases where several FOO-ish classes live in distinct modules but have the same local name: discovering which class triggered the problem may require nontrivial code analysis.

Thus I propose to extend this error message so that it reports the module name, i.e. abstract class BAZ.BAR.FOO, instead.

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Linked PRs

• gh-156683

此 issue 將抽象類別的 TypeError 訊息定為切入點；先檢視連結的 PR gh-156683，以了解目前提議的範圍。確認完成後的行為會在此錯誤中回報類別的模組限定名稱，同時不會遺失抽象方法的詳細資訊。