feat(signature-type): add missing microsoft-defender signature types (#335)

[guzmud]

Proposed changes

• Adding missing signature types used by the collector microsoft-defender

Testing Instructions

1. Step-by-step how to test
2. Environment or config notes

Related issues

• Closes feat(signature-types): adding signature types used in microsoft-defender #335

Checklist

• I consider the submitted work as finished
• I tested the code for its functionality
• I wrote test cases for the relevant uses case
• I added/update the relevant documentation (either on github or on notion)
• Where necessary I refactored code to improve the overall quality
• For bug fix -> I implemented a test that covers the bug

Further comments

[Copilot]

🟡 Changes recommended

New public enum values were added without corresponding unit tests to lock in the expected string values and prevent regressions.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

Adds the missing SignatureTypes enum entries needed by the microsoft-defender collector so collectors and other components can share a consistent signature vocabulary.

Changes:

• Added process_name, command_line, file_name, hostname, ipv4_address, and ipv6_address to SignatureTypes.
• Aligns the Python client’s signature type vocabulary with what microsoft-defender already uses.

File summaries

File	Description
pyoaev/signatures/types.py	Extends SignatureTypes with additional values required by microsoft-defender.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

[Kakudou]

LGTM, gonna need a real analysis of usage when we gonna rework that into a SDK :D.

Ty !