Client componets don't need to unsubscribe when ref is destroyed

[evaera]

1. destroy part on server
2. component on server destroyed
3. component on client destroyed (independently of server, since it uses collectionservice)
4. component on client tries to tell server something, (i'm assuming unsubscribe) but error on server since cannot deserialize already destroyed component on part

[evaera]

Is it even possible to determine this though? We have to consider StreamingEnabled. Refs disappear from the client all the time and those should still unsubscribe. How do we know when the server actually properly destroyed a ref (and how do we know in time)?

[sayhisam1]

Could keep the server error silent (or optional) - the only impact it really has is that it spams output when destroying parts.

[evaera]

Parts are destroyed when they are streamed out. Current thinking is we need to ignore this on the server. We can still emit warnings for failed subscribe events.