Pinned objects can still be grabbed (newLoader)

[stalgiag]

Description
Pinned objects can be grabbed and moved when working behind newLoader. A cursory search suggests that the Pinned component is not always successfully added to the entity (either on first pinning or on load from reticulum) causing checks like this one to behave unpredictably.

To Reproduce
Steps to reproduce the behavior:

1. Go to a room with newLoader URL param
2. Add an object to the room
3. Pin the object
4. Try to move the pinned object

[stalgiag]

The only place where a Pinned component is added to an entity is in the Aframe "pinnable" component. It appears that this system is now disconnected from the rest of the new ECS code. There is no pinnable jsx entity attribute.

Instead of looking for a Pinned component, the objectMenuSystem decides whether to display the "pin" or "unpin" button based on the isPinned() check instead. We can get the expected interaction behavior by replacing hasComponent(world, Pinned, eid) checks in interaction systems with isPinned().

I am still working to wrap my head around which parts of the codebase are currently active on the newLoader path but my intuition is that checking if the server is the creator of an entity to determine state is not an ideal solution as it deviates from the ecs pattern.

[stalgiag]

This relates to task with promotion permissions on ECS path. To handle both issues, I am going to make a pinnable system.

[Exairnous]

Looks like this bug now affects the current loader.

[Exairnous]

@johnshaughnessy ^