Add wp-cron.php to exclusion list for request handler

[dsturm]

This PR includes wp-cron.php request in the exclusion list for the request handler introduced in #339.

[iniznet]

Wouldn't it be better if we also allowed people to customize this through a filter hook, like:

if (Str::contains(
    $request->getRequestUri(),
    apply_filters('acorn/router/ignore_request_paths', [
        '/wp-comments-post.php',
        '/wp-cron.php',
        '/wp-login.php',
        '/wp-signup.php',
        '/wp-admin/',
    ])
)) {
    return; // Let WordPress handle these requests
}

I have a case related to the new router, where I set a cookie through a custom route that has not yet been migrated to the Laravel router and ended up getting cleared by the router.

[retlehs]

A filter is a good idea 👍 We also want to move away from the hardcoded paths and use admin_url(), login_url(), etc

@dsturm Were wp-cron.php requests failing for you without this change?

[dsturm]

@retlehs Nope, not yet. But imo the WP Cron shouldn't be handled by anything outside WordPress core - should it?

[retlehs]

The paths added in #339 are for files that rely on the use of cookies, so wp-cron.php shouldn't be affected

@broskees mentioned on our Discord server that he might have a different fix to replace the code introduced in #339, since the response classes handle cookies too and the bootloader changes aren't accounting for that