Proper handling of limited objects data

[eliasbruvik]

When we request a list of data objects from the API (where we ask the API to use ETP), the data we get back is very reduced. We only get the uid, name and maybe some extra metadata but not the full object. We need to ensure that this does not break anything in our frontend.

Possible issues, test for other issues and fill out this list:

• Null pointers on fields we always expect to get a value from with SOAP.
• We pass the object from the list to the context menus which in turn is passed to for example the properties modal where the user can edit fields of the object. We need to rework this approach to actually fetch the full object (possibly use useGetObject).
• Remove updatePartialObjects from useGetObject as we want a clearer difference between the objects in an object list and the object itself. Ensure this does not cause further issues. We possibly need to look at refreshObjectQuery usages and see if we rather need to use the plural refreshObjectsQuery to ensure all relevant data is properly invalidated and reloaded.
• Ensure that "hidden" functionality works with limited data. Examples, but probably more we need to check:
  • Multiple Log Selection
  • Search views

Split this into subtasks if there's no logical common fix.