Add CTI Transmute conversion object template

[adulau]

Motivation

• Provide a MISP object to record CTI conversions performed by CTI Transmute, mapping the requested database fields into MISP object attributes for interoperability and traceability.
• Ensure reasonable defaults and constrained values for conversion direction and output format to make the object user-friendly and less error-prone.

Description

• Add a new object template objects/cti-transmute-conversion/definition.json that models the conversion record and includes name, description, input_text, conversion_type, output_text, created_at, updated_at, public, uuid, is_active, deleted_at, and detail_url attributes.
• Map database fields to appropriate MISP attribute types (e.g. integer for user_id, text for name/description/input_text/output_text, datetime for timestamps, boolean for public/is_active, uuid for uuid, and link for detail_url).
• Add sane_default values and values_list constraints for conversion_type (MISP_TO_STIX, STIX_TO_MISP) and output_type (STIX, MISP), plus sensible defaults for input_text and output_text placeholders, and include required fields name, input_text, conversion_type, and output_text.
• Register the new object in README.md object listing and set object version and generated uuid in the template metadata.

Testing

• Ran jq . objects/cti-transmute-conversion/definition.json >/dev/null and jsonschema -i objects/cti-transmute-conversion/definition.json schema_objects.json which validated the new template against the repository schema and succeeded.
• Executed repository validation scripts ./unique_uuid.py and ./validate_all.sh (which runs ./jq_all_the_things.sh and schema checks for all objects) and all checks completed successfully.

---

Codex Task