Fix Wiz vulnerability upload timeout and python-dotenv dependency check

[iteuscher]

Summary

• Wiz vulnerability upload timeout: bump the Paramify assessment-intake upload timeout from 120s to 600s in fetchers/wiz/wiz_vulnerabilities_findings.py. The vulnerability CSV (~12 MB / ~5.4k findings) takes ~2.5 min to upload; the fetch succeeded but the upload was dying with a write operation timed out error.
• Dependency check false positive: 3-run-fetchers/run_fetchers.py checked the catalog dependency python-dotenv by importing that literal name, which always failed and produced a misleading python-dotenv not found warning. It now maps the dependency to its real module name (dotenv).

Context

While running the Wiz fetchers through the menu flow (main.py -> option 3 -> run_fetchers.py), the scripts resolved and ran correctly (the prior "Script not found" issue was caused by a stale, git-ignored evidence_sets.json, not the tracked catalog, which is already correct on main). These two code-level fixes are the changes that belong in the repo.

Test plan

• wiz_vulnerabilities_findings.py completes the Paramify upload of the full ~12 MB CSV without timing out.
• run_fetchers.py dependency check prints ✓ python-dotenv instead of a false "not found" warning.
• python3 -c "import run_fetchers" imports cleanly; no linter errors.

Notes (not in this PR)

• evidence_sets.json and customer_config.json are git-ignored local artifacts; their Wiz entries were reconciled locally to the canonical (wiz_issues_report / wiz_vulnerabilities_findings) naming used by the tracked catalog.
• A stray, untracked root-level evidence_fetchers_catalog.json (old naming scheme) was removed locally.
• wiz_issues_report requires WIZ_ISSUES_PARAMIFY_ASSESSMENT_ID in .env; that key currently appears to be missing from the local .env and must be restored (no .env changes are included here).

Made with Cursor