PLUG-4654: Update Microsoft Defender Icon

[jame2O]

📋 Summary

This PR updates the icon for Microsoft Defender to an SVG. This fixes a bug where the icon was being cropped on squaredup.com

🔗 Related issue(s)

---

🧩 Plugin details

• Plugin name:
• Type of change:
  • Bug fix
  • New datastream
  • Enhancement to existing datastream
  • Performance improvement
  • Documentation / metadata / logo
  • Other (please describe):

---

⚠️ Breaking changes

Does this PR introduce any breaking changes?

• No
• Yes (please describe):

If yes, describe:

• What breaks
• Who is impacted
• Any migration steps

---

📚 Documentation

• Documentation updated
• No documentation changes needed

---

✅ Checklist

• No secrets or credentials included
• Plugin, datastream and UI naming follow SquaredUp guidelines
• I agree to the Code of Conduct

[clarkd]

@claude review

[clarkd]

@claude review once

[github-actions]

🧩 Plugin PR Summary

📦 Modified Plugins

• plugins/MicrosoftDefender/v1

📋 Results

Step	Status
Validation	✅ Passed
Deployment	🚀 Deployed

🔍 Validation Details

✅ microsoft-defender

{
  "valid": true,
  "pluginName": "microsoft-defender",
  "pluginType": "hybrid",
  "summary": {
    "Data Streams": 12,
    "Import Definitions": 1,
    "UI Configuration": true,
    "Has Icon": true,
    "Has Default Content": true,
    "Config Validation": true,
    "Custom Types": true
  }
}

[claude]

Icon swap with the requested 1.0.3 version bump — addresses the prior versioning feedback.

Extended reasoning...

Overview

This PR replaces plugins/MicrosoftDefender/v1/icon.png with icon.svg and bumps metadata.json from 1.0.0 to 1.0.3. Per the timeline, the reviewer (clarkd) requested 1.0.3 specifically to cover several previously-unbumped Defender plugin changes that landed on main, and the current diff now reflects that exact version.

Security risks

None. The change is purely a visual asset swap plus a version-number bump. No code paths, authentication, secrets, or data flow are touched.

Level of scrutiny

Low. This is a documentation/branding/metadata-only change: removing a PNG, adding an SVG (with a viewBox per the inline discussion), and bumping the plugin version. The previous reviewer feedback about the version was the only outstanding concern, and it has been addressed in the latest commit.

Other factors

The plugin validation/deployment check from the repo's CI summary passes. My prior bot review explicitly called out the 1.0.1 → 1.0.3 gap; the head of the branch now ships 1.0.3, so the unresolved comment is resolved by the code itself. No new code was introduced that would warrant deeper analysis.