Add generic physical-object and physical-item MISP templates

[adulau]

Motivation

• Provide analyst-friendly, generic templates to describe physical objects and tracked items for HUMINT and physical-collection workflows (e.g., evidence in a rented car) and address issue Add a physical/item object template #376.
• Allow consistent capture of both observable object properties (appearance, identifiers, materials) and custody/handling metadata (case linkage, seals, storage) to improve investigative documentation and sharing.

Description

• Added objects/physical-object/definition.json which defines a generic physical object with attributes such as object-type, serial-number, rfid, barcode, location-found, acquisition-date, object-picture, material, dimensions, weight, quantity, and related metadata, and a requiredOneOf to ensure at least one identifier/description is present.
• Added objects/physical-item/definition.json which defines an analyst-centric item template with attributes such as item-number, case-number, collection-date, collector, item-status, packaging, seal-number, storage-location, owner, item-picture, and estimated-value with required fields item-number and description.
• Both templates are placed under the repository objects/ directory and include UUIDs and initial version fields.

Testing

• Ran ./jq_all_the_things.sh which formatted and validated JSON, though the environment reported uuidparse: command not found as a warning while the script completed its work.
• Verified JSON validity with jq . objects/physical-object/definition.json and jq . objects/physical-item/definition.json, both of which succeeded.
• Ran python unique_uuid.py which completed in this environment (no duplicate UUIDs reported for the new files).
• Ran ./validate_all.sh which exited with an error in this environment because it enforces a clean post-formatting git tree and detected uncommitted changes (the repository check failed, not the object schema validation).

---

Codex Task