fix bug

[gdmjali]

Why

When moving a knowledge source between two shared spaces, it doesnt get moved when pressing move. This fixes the issue.

[axelander]

Thanks for digging into this and putting together a fix , it helped surface some deeper issues in how resource moving works.

Right now, move_collection_to_space calls import_group_to_space, which only links the knowledge to the target space rather than actually moving it. Switching to move_group_owner_to_space would move ownership, but
introduces other complications.

The core issue is that user_id on the collection never changes during a move. The original creator remains the owner even if they no longer have access to the target space, resulting in orphaned ownership and
unclear access patterns. The same applies to websites, where move_website_to_space explicitly does not change ownership either.

Given these open questions around ownership and access control, we're going to remove this functionality for now and revisit it once we have a clearer design in place. If there's a strong need for this, we'd appreciate proposals on how ownership transfer and access should be handled.