Change event typing, and other fixes

[Liam-DeVoe]

• event(value, payload) accepts any string-coercible value in payload, and the type hint of Any now reflects this.
• Following Handle unhashable modules in constants collection #4661, modules are now tracked by id instead of hash, which is equivalent for ModuleType and cleaner otherwise.

b33e473 is the result of FORMAT_ALL=true ./build.sh format. It's a bug that we didn't format all files at tool bump, but I don't have a root cause narrowed down.

[Zac-HD]

I think this is a case where I actually prefer our type annotations to be stricter than the runtime logic - while more exotic payloads 'mostly work', it'd be nice to keep weird problems with string conversion as the user's problem.

For the same usage-hint reason that we say value: str, let's keep payload: str | int | float.

[Liam-DeVoe]

I disagree with this. My interpretation of your position: type hints have two purposes; documentation, and correctness. We type payload: str | int | float to communicate "these are the normal types you'll be passing" to a user seeing event for the first time. But this comes at the expense of requiring other users to add type: ignore at their usage sites. Since we explicitly document that string-convertible objects are valid, I think the types should reflect this.

What about payload: SupportsStr, which is a typing protocol that requires __str__? I hadn't realized we do the same conversion for value, so I'd also support value: SupportsStr.