[Feature Request] Allow assets to be assigned to another asset as a default location

[niedfa]

Description
Currently, in Snipe-IT, an asset can’t be assigned to another asset as its default location. This feature would be highly beneficial in scenarios where assets are physically stored within other assets, such as specific devices installed in a movable server rack or tools placed in a toolbox. By enabling assets to be assigned to other assets as their default location, users can create a more intuitive and structured asset hierarchy directly within the system.
One key limitation of relying solely on the “Checkout” function is that when the “Checkin” function is used, the asset is checked back into the default location or an other location rather than being reassigned to its previous parent asset. This behavior undermines the ability to maintain accurate relationships between assets. With this feature, users would have the flexibility to check out either the container asset as a whole or the individual assets within it.
Proposed Solution
Key features of this enhancement could include:
• Modify the "Default Location" field on the asset creation/editing page to enable users to choose between assigning the asset to a location or to an other asset as its default location.
• Implement functionality similar to the "Checkout" feature, where users can select between assigning to a user, a location, or another asset.
Conclusion
This feature would enhance Snipe-IT’s flexibility by allowing assets to recognize other assets as their default location. This functionality would better reflect real-world asset management scenarios and provide a more user-friendly experience. Thank you for considering this request! Please let me know if additional information or clarification is needed.

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.