Fix PowerShell scripts identified during comprehensive testing

- Fixed sf-apex-run.ps1 parameter sets to allow proper help functionality
- Fixed sf-data-export.ps1 to not pass unsupported --verbose flag to sf commands
- Fixed sf-data-import.ps1 command structure to use correct sf data import bulk/tree commands
- Removed --verbose flag from sf data commands as they don't support it
- All scripts now properly work with their respective parameter combinations
- Comprehensive testing completed with all functionality verified

Testing results:
✅ sf-check.ps1 - Working correctly
✅ sf-org-info.ps1 - Working correctly
✅ sf-web-open.ps1 - Working correctly
✅ sf-apex-run.ps1 - Fixed parameter sets, now working
✅ sf-deploy.ps1 - Working correctly
✅ sf-dry-run.ps1 - Working correctly
✅ sf-data-export.ps1 - Fixed --verbose flag issue, now working
✅ sf-data-import.ps1 - Fixed command structure, now working
✅ sf-retrieve.ps1 - Working correctly
✅ sf-test-run.ps1 - Working correctly
✅ sf-logs-tail.ps1 - Working correctly
✅ sf-org-create.ps1 - Working correctly

sf-data-export.ps1

@@ -262,10 +262,8 @@ if ($TargetOrg) {
 Write-Host "Output format: $Format" -ForegroundColor Cyan
 Write-Host "Output file: $Output" -ForegroundColor Cyan
 
-# Add verbose flag if requested
-if ($VerboseOutput) {
-    $sfArgs += "--verbose"
-}
+# Note: sf data commands don't support --verbose flag
+# VerboseOutput only affects the script's own output (query preview)
 
 # Display export information
 Write-Host ""