fix: do not remap core meta caps in access checks

[faisalahammad]

AI disclosure: this PR was written with GLM 5.3 flash assistance, reviewed and tested by me.

Description

Item-level access checks in pods_access_map_capabilities() were rewriting the canonical meta capabilities read_post, edit_post, and delete_post through the post type capability object before passing them to WP_User::has_cap(). For a pod with a page capability type, read_post becomes the literal string read_page. When that post type also has meta capability mapping disabled ("Full User Capabilities" unchecked), map_meta_cap() in WP 7.1 core reads the nonexistent $post_type->cap->read_page property and triggers a PHP warning for logged-out visitors.

The fix keeps those three meta caps canonical and lets core resolve them against the capability object itself, which it already does for every other path. I traced each capability flavor (post, page, custom) with mapping on and off: the outcomes are identical in every combination except the broken one, where the warning disappears.

Backward compatible: yes, no breaking changes.

Related GitHub issue(s)

Fixes #7619

Testing instructions

1. Create a Custom Post Type extended by Pods with "Page" as the capability type and "Full User Capabilities" (meta capability mapping) disabled.
2. Add a published item for that post type and log out of WordPress.
3. With WP_DEBUG_DISPLAY enabled, visit the single item front-end view on WP 7.1.
4. Before this PR: PHP Notice: Undefined property: stdClass::$read_page in wp-includes/capabilities.php appears.
5. After this PR: no warning appears, and admin/author read access to the item still works as before.

Tested manually: confirmed this resolves the reported issue.

Screenshots / screencast

Not applicable, no UI changes.

Changelog text for these changes

Bug: Item-level access checks no longer rewrite read_post, edit_post, or delete_post through the post type capability object, which prevents a PHP warning from map_meta_cap when a post type with a page capability type has meta capability mapping disabled. #7619 (@sc0ttkclark)

PR checklist

• I have tested my own code to confirm it works as I intended.
• My code follows the WordPress Coding Standards.
• My code follows the WordPress Inline Documentation Standards.
• My code includes automated tests for PHP and/or JS (if applicable).