fix: house item transfer logic and bed sleeper reset on invalid state

[dudantas]

Description

This PR addresses two related issues in the house transfer and load logic.

1. Improves the behavior of House::collectMovableItemsFromContainer to ensure the container itself is moved after its content is evaluated and collected, preserving nested container structure and avoiding data loss.

2. Adds logging during house item transfer to show all items that were found and moved, including their names, IDs, and positions, improving traceability and debugging.

3. Adjusts bed loading logic to clear the sleeper from a bed if its configuration is invalid or incomplete during the house map load phase, fixing potential stuck player bugs.

Behaviour

Actual

• Items inside nested containers were not being transferred correctly, sometimes resulting in missing or skipped items.
• Beds with missing components would retain invalid sleeper references, causing unexpected behavior.
• No logs were provided to track transferred items clearly.

Expected

• Items, including those inside containers, are properly transferred with the container.
• Beds with invalid states do not retain sleepers.
• Logs clearly indicate which items were transferred, their location, and ID.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested

Tested on a local dev server with:

• Multiple houses containing nested containers.
• Invalid beds with missing components.
• Log output validated during transfer.
• Checked depot inbox to ensure all items were received.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I checked the PR checks reports
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud