Add custom errors for common use cases of using a component after being disposed

[mairatma]

Calling functions on a component after it's been disposed will almost always throw an error, since disposing will cause the component to get rid of listeners and variables so that the garbage collector can work.

The error that gets thrown is hard to debug though, since it doesn't say anything about the component being disposed, it's usually a type error due to calling something on data that was removed, for example. We should have custom errors to help debug the most common use cases easily (like calling setState or setting state directly).