Remove dedicated section, keep only updated configuration examples

- Remove the standalone Native HAProxy Redirect section
- Keep the updated configuration examples with native redirects and performance optimizations

Author: LaurenceJJones

crowdsec-docs/unversioned/bouncers/haproxy_spoa.mdx

@@ -219,24 +219,6 @@ recaptcha
 turnstile
 ```
 
-#### Native HAProxy Redirect (Performance Optimization)
-
-The HAProxy SPOA bouncer now supports native HAProxy redirects for successful CAPTCHA validation, providing better performance and reduced Lua overhead:
-
-```haproxy
-## Handle 302 redirect for successful captcha validation (native HAProxy redirect)
-http-request redirect code 302 location %[var(txn.crowdsec.redirect)] if { var(txn.crowdsec.remediation) -m str "allow" } { var(txn.crowdsec.redirect) -m found }
-
-## Call lua script only for ban and captcha remediations (performance optimization)
-http-request lua.crowdsec_handle if { var(txn.crowdsec.remediation) -m str "captcha" }
-http-request lua.crowdsec_handle if { var(txn.crowdsec.remediation) -m str "ban" }
-```
-
-This approach provides:
-- **Native 302 redirects**: Uses HAProxy's built-in redirect functionality instead of Lua
-- **Performance optimization**: Lua script is only called for `ban` and `captcha` remediations
-- **Reduced overhead**: Eliminates unnecessary Lua processing for `allow` decisions
-- **Better scalability**: Native HAProxy operations are more efficient than Lua-based solutions
 
 ### Prometheus Metrics