Add generic malicious-website object template

[adulau]

Motivation

• Provide a reusable object to represent malicious websites outside phishing-specific workflows (malware delivery, scam landing pages, exploit hosting, C2 panels, etc.).
• The existing phishing object is phishing-centric (Phishtank/takedown/verification fields) and would not be a clean fit for non-phishing malicious-site use-cases.

Description

• Add objects/malicious-website/definition.json containing attributes url, domain, hostname, ip, threat-type, status, reason, source, and external-analysis to capture core indicators and contextual metadata.
• Use requiredOneOf on core network identifiers (url, domain, hostname, ip) so the template is flexible and not overly prescriptive.
• Follow repository conventions (kebab-case attribute names, descriptive meta-category, uuid, and version).

Testing

• Ran ./jq_all_the_things.sh successfully to normalize JSON files and verify formatting.
• Ran ./validate_all.sh which failed in this environment due to the missing uuidparse binary and the script expecting a clean post-format git state; the new object JSON itself is valid and follows repository schema conventions.

---

Codex Task

[adulau]

To solve #268