Add WordPress plugin for LibreCaptcha integration

[hrj]

This PR introduces a WordPress plugin to integrate LibreCaptcha into common WordPress forms (Login, Registration, Comments) as well as any custom page via shortcode. It adds an administrative settings page to configure the API integration and handles secure server-to-server answer verification.

---

PR created automatically by Jules for task 7710305599071125477 started by @hrj

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[hrj]

In the settings page for the plugin, add a test button which will fetch a CAPTCHA from the server and show it, along with an input field and a check button. When the check button is clicked, the input will be validated through the API. This will help to quickly check the LC server and plugin setup.

[google-labs-jules]

In the settings page for the plugin, add a test button which will fetch a CAPTCHA from the server and show it, along with an input field and a check button. When the check button is clicked, the input will be validated through the API. This will help to quickly check the LC server and plugin setup.

I've added the test button functionality to the settings page as requested. It allows administrators to fetch a test CAPTCHA and validate an answer to confirm their LC server integration is working correctly.

[hrj]

The test functionality should make the API calls on the server side not in the client, because the LC server may not be accessible to the client.

Also, add an option in the plugin settings to specify the auth key (optional).

[google-labs-jules]

The test functionality should make the API calls on the server side not in the client, because the LC server may not be accessible to the client.

Also, add an option in the plugin settings to specify the auth key (optional).

I've added the optional lc_auth_key setting. Additionally, I've moved the test functionality to the server-side. The settings page now makes an AJAX request to the WordPress backend (wp_ajax_lc_test_load and wp_ajax_lc_test_check), which in turn calls the LibreCaptcha server using the configured server URL and auth key.

[hrj]

Define OPTIONS method handler on all API endpoints (as and where appropriate). This is because in certain browser emulated environments, the server side code running inside a browser causes an issue of OPTIONS request before the actual API request.

[google-labs-jules]

Define OPTIONS method handler on all API endpoints (as and where appropriate). This is because in certain browser emulated environments, the server side code running inside a browser causes an issue of OPTIONS request before the actual API request.

I've added CORS OPTIONS preflight handlers to the /v2/captcha, /v2/media, and /v2/answer API routes to ensure they correctly serve the Access-Control-Allow- headers when accessed from browser environments.

[hrj]

Just like the test captcha component in settings, ensure that all LC API calls in the plugin are done through backend PHP, not frontend javascript.

[google-labs-jules]

Just like the test captcha component in settings, ensure that all LC API calls in the plugin are done through backend PHP, not frontend javascript.

I've refactored the CAPTCHA rendering logic in render_captcha(). It now performs the API call to /v2/captcha using server-side PHP (wp_remote_post), bypassing the need for any frontend Javascript requests. The resulting image and ID are injected directly into the HTML structure.

[hrj]

You have added an OPTIONS builder to picoserve. This can be used to simplify the handler definitions in Server.scala. Also, there is code repetition in handling of OPTIONS method across endpoints. Try and refactor to a common function.

[google-labs-jules]

You have added an OPTIONS builder to picoserve. This can be used to simplify the handler definitions in Server.scala. Also, there is code repetition in handling of OPTIONS method across endpoints. Try and refactor to a common function.

I've refactored Server.scala to use the .OPTIONS builder from picoserve instead of a custom .handle() method. I also abstracted the OPTIONS logic into a common getOptionsResponse function. Finally, I refactored picoserve so it correctly supports multiple handlers on the same path (e.g. one for GET/POST and one for OPTIONS). Tests are passing!