Potential fix for code scanning alert no. 1: Information exposure through an exception

[tonytech83]

Potential fix for https://github.com/tonytech83/Inventory/security/code-scanning/1

To fix this safely, keep the bulk-import behavior and per-row success/failure reporting, but stop returning raw exception details to the client.

Best approach (without changing functional behavior):

1. In inventory/devices/utils.py, add server-side logging.
2. In the except Exception as e: block, log the exception with context (e.g., device name/row info) using logger.exception(...).
3. Replace "error": str(e) in results with a generic message like "Device could not be imported due to invalid data.".

This preserves:

• Row-level error reporting for clients (status: Error still present),
• Operational debugging for developers (full traceback in server logs),
• Existing API shape (results still includes an error field).

Files/regions to change:

• inventory/devices/utils.py: import logging, define module logger, and update exception handling block in create_devices_form_upload.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.