Fix syncing components on the client entity when the client doesn't have a position

The following discussion from !970 (merged) should be addressed:

• @Imbris started a discussion: (+1 comment)

  Sounds like there is a bug with the player component not being sent initially once the client is registered. Probably my fault.