Fix clash.yaml: move orphaned expected-status back into health-check block

expected-status: 204 ended up after the rules section instead of
inside proxy-providers.sub.health-check where it belongs.

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

assets/clash/clash.yaml

@@ -28,6 +28,7 @@ proxy-providers:
       interval: 300
       timeout: 5000
       lazy: true
+      expected-status: 204
 
 
 
@@ -281,6 +282,3 @@ rules:
   - RULE-SET,python,🔓 NO VPN
   - RULE-SET,geoip-ru,🔓 NO VPN
   - MATCH,🌍 VPN
-
-      expected-status: 204
-