Improve the UX of our property editor component

[agarny]

Although we can edit a property, the overall UX is anything but ideal. So, we would need to:

• use focustrap to keep the focus in the property editor (right now, to press Tab / Shift+Tab will eventually leave the property editor);
• enter editing mode upon selecting a row;
• enter editing mode upon navigating to the previous/next row using the ↑/↓ keys;
• enter/exit editing mode using the Enter key; and
• have support for different types of properties (e.g., a double, a non-zero double, an unsigned integer, an item from a list).