Enforce strict two-character option scheme across all wrapper scripts

- Removed long options from input parsing in all bash scripts
- Updated all help texts to show only two-character options
- Fixed error messages to reference short options only
- All scripts now reject long options like --help, --verbose, --target-org
- Maintained internal use of long sf CLI commands (e.g., --target-org passed to sf)
- Updated README.md documentation to reflect two-character scheme only
- Scripts affected: sf-retrieve, sf-test-run, sf-data-import, sf-data-export
- PowerShell scripts already used correct two-character parameter scheme
- All wrapper scripts now have consistent user interface

This ensures strict consistency in the two-character option scheme
while maintaining backward compatibility for the sf CLI commands themselves.

sf-apex-run

@@ -62,7 +62,7 @@ fi
 # Parse arguments manually for two-character options
 while [[ $# -gt 0 ]]; do
   case $1 in
-    -to|--target-org)
+    -to)
       if [[ -n "${2:-}" && ! "$2" =~ ^- ]]; then
         ORG="$2"
         shift 2
@@ -72,7 +72,7 @@ while [[ $# -gt 0 ]]; do
         exit 1
       fi
       ;;
-    -fl|--file)
+    -fl)
       if [[ -n "${2:-}" && ! "$2" =~ ^- ]]; then
         APEX_FILE="$2"
         shift 2
@@ -82,7 +82,7 @@ while [[ $# -gt 0 ]]; do
         exit 1
       fi
       ;;
-    -cd|--code)
+    -cd)
       if [[ -n "${2:-}" ]]; then
         APEX_CODE="$2"
         shift 2
@@ -92,7 +92,7 @@ while [[ $# -gt 0 ]]; do
         exit 1
       fi
       ;;
-    -hp|--help)
+    -hp)
       show_help
       exit 0
       ;;