BIM: when an object is created out of a base object in a container, ghost base objects appear

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Problem description

Steps to reproduce:

1. Create a BIM file with the customary object hierarchy (Site > Building > Levels) and a group inside one of the levels. You can use the ready-made [Levels_ghosts.zip](https://github.com/user-attachments/files/19904618/Levels_ghosts.zip) file as well. It first needs to be uncompressed.
2. Switch to the BIM workbench
3. Select the group inside the level and create a rectangle base object
4. The base object is created outside of the group => FAIL, but not the subject of this issue
5. Move the base object inside the group it was intended to be in
6. Select the base rectangle object and create a BIM object (e.g. a wall) from it
7. The host object (wall) is created outside of the group => FAIL, but not the subject of this issue
8. Notice there are now two base objects on the tree: one within the host object (wall) and a ghost one inside the group. Moving the host object to be inside the group does not remove the ghost object => **FAIL**

https://github.com/user-attachments/assets/836da7db-8624-4d21-a251-0b858e2a6c49

### Workaround

The workaround is to **drag both the ghost base object and the host object to the root of the tree**. Then the ghost object disappears and the host object can be moved back to its original group:

https://github.com/user-attachments/assets/71908bc2-c606-4c66-aaa3-786194576d7e

### Full version info

```shell
1.1.0dev, but the issue has been there since 0.21 at least.
```

### Subproject(s) affected?

BIM

### Anything else?

- It happens with multiple types of containers: groups, levels (BuildingPart), etc.
- It happens to other BIM objects, not only walls. Arrays for instance also exhibit this behavior
- The workaround is particularly tedious when the size of the tree is significant, as it often happens in BIM models

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct