Remove undocumented 'proxies' configuration option

Simplify configuration by removing the legacy 'proxies' field from
the YAML routes structure. Users should use 'reverse_proxies' instead,
which provides the same functionality plus method exclusion support.

This removes:
- Proxies struct from YAML configuration
- Processing loop for yamlConfig.Routes.Proxies

Only 'reverse_proxies' is now supported, which was already the
documented and recommended approach.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: rubys

cmd/navigator/main.go

@@ -275,11 +275,6 @@ type YAMLConfig struct {
 			From string `yaml:"from"`
 			To   string `yaml:"to"`
 		} `yaml:"rewrites"`
-		Proxies []struct {
-			Path    string            `yaml:"path"`
-			Target  string            `yaml:"target"`
-			Headers map[string]string `yaml:"headers"`
-		} `yaml:"proxies"`
 		FlyReplay []struct {
 			Path    string   `yaml:"path"`
 			Region  string   `yaml:"region"`
@@ -1475,15 +1470,6 @@ func ParseYAML(content []byte) (*Config, error) {
 		}
 	}
 
-	// Convert proxy routes
-	for _, proxy := range yamlConfig.Routes.Proxies {
-		config.ProxyRoutes[proxy.Path] = &ProxyRoute{
-			Pattern:    proxy.Path,
-			ProxyPass:  proxy.Target,
-			SetHeaders: proxy.Headers,
-		}
-	}
-
 	// Convert fly-replay routes
 	for _, flyReplay := range yamlConfig.Routes.FlyReplay {
 		if re, err := regexp.Compile(flyReplay.Path); err == nil {