refactor: type(x).__name__ => x.__class__.__name__

[Enegg]

Summary

This PR unifies the style of access to a value's type's name, replacing type(x).__name__ with x.__class__.__name__ (since the latter has been used more often)
Also moves a type guard at disnake/ext/tasks/init.py#L125-L127 higher up, so it can fail quicker.

Checklist

• If code changes were made, then they have been tested
  • I have updated the documentation to reflect the changes
  • I have formatted the code properly by running uv run nox -s lint
  • I have type-checked the code by running uv run nox -s pyright
• This PR fixes an issue
• This PR adds something new (e.g. new method or parameters)
• This PR is a breaking change (e.g. methods or parameters removed/renamed)
• This PR is not a code change (e.g. documentation, README, ...)

[read-the-docs-community]

Documentation build overview

📚 disnake | 🛠️ Build #33399248 | 📁 Comparing 6206047 against latest (7ee96b8)

  🔍 Preview build  

47 files changed · ± 47 modified

± Modified

• index.html
• api/abc.html
• api/activities.html
• api/app_commands.html
• api/app_info.html
• api/audit_logs.html
• api/automod.html
• api/channels.html
• api/clients.html
• api/components.html
• and 37 more...

[onerandomusername]

There's a risk to this as __class__ can be overridden by user code, and the majority of these are used in instances where the instance check failed and a type could be an arbitrary type.

I'm not sure unification of these is necessary in one big go, but we should probably standardize on a specific type for future code.

[Enegg]

The PR could go the other way and replace .__class__ with type().
Just wanted to standardize it as a prelude to standardizing exception messages that I have a branch for

[shiftinv]

There's a risk to this as __class__ can be overridden by user code

type(x) appears to be completely equivalent to x.__class__ even when overridden by user code:
https://github.com/python/cpython/blob/95296a9d40aa2d58502a09e86e2a93c03df23366/Objects/typeobject.c#L5070-L5080
https://github.com/python/cpython/blob/95296a9d40aa2d58502a09e86e2a93c03df23366/Objects/typeobject.c#L7308-L7312
All in all this seems fine. There isn't a way around it, but I also think we don't need one.

[shiftinv]

Would you mind updating this PR and resolving merge conflicts? ty c: