#1783 : Duplicate Amplitude Events Triggered During Migration

[AbhijeetThakur]

What this PR does / why we need it

• Extract VM names from the migration plan spec and send separate Amplitude events for each VM being migrated, including the VM name in the event properties alongside existing migration metadata.
• Implements tracking for delete operations across VMware credentials, PCD credentials, migrations, and agents. Updates AMPLITUDE_EVENTS.md to reorganize documentation into user journey-based sections with implementation status tracking.

Which issue(s) this PR fixes

fixes #1783

• Duplicate Amplitude Events Triggered During Migration #1783

Testing done

Screencast.from.09-04-26.05.29.05.PM.IST.webm

Migration with a single VM

[OmkarDeshpande7]

lgtm

[github-actions]

✅ Security Vulnerability Summary

No change in security posture

📊 Overall Changes

Metric	Count
Total Added	0
Total Fixed	0
Net Change	0

🔍 Detailed Breakdown

📦 Gosec (Static Analysis)

Current	Baseline	Added	Fixed	Method
0	0	0	0	artifact

📦 Trivy (Dependency Scan)

Current	Baseline	Added	Fixed	Method
8	8	0	0	artifact

📋 Baseline Methods

• 📦 artifact: Used stored report from main branch
• 🔄 live_scan: Scanned base branch in real-time
• ⚠️ no_baseline: No baseline available (all vulnerabilities treated as new)

---

Only HIGH and CRITICAL severity vulnerabilities are tracked
Baseline: 80b5869dbf4a48e61cc02e75edaa9222784e4eed