feat(collector): support description and tags on the security platform auto-created by collectors #319

Problem

When a collector declares a collector_platform, the CollectorDaemon automatically upserts the associated security platform asset. The upsert payload only carries the name, external reference, type and logos - no description and no tags - so the read-only security platform cards created by collectors are essentially empty in the OpenAEV UI.

Proposal

Let collectors provide a description and tags for their auto-created security platform through two new optional configuration keys, handled centrally in CollectorDaemon._setup:

• collector_platform_description: passed as asset_description in the security platform upsert.
• collector_platform_tags: list of tag names (or a comma-separated string); each tag is upserted (neutral grey color) and the resulting ids are passed as asset_tags.

Both keys are optional: when absent, the upsert payload is unchanged, so existing collectors keep their current behavior. ConfigLoaderCollector also gains matching optional platform_description / platform_tags fields so pydantic-based collector configs can declare them.

The companion sweep in OpenAEV-Platform/collectors sets proper defaults for all 19 collectors that register a security platform.