Repair Tool: Compare filterable/cachable queries with direct DB queries before editing config

[pdclark]

Description

Repair Tool, when checking Pods data structure, at times ran queries which could be altered by filters, including object and transient cache.

This draft compares each query to a direct database query, and if consistent, pauses the repair and surfaces a (currently long-winded) message indicating plugins may be effecting data structure.

If the query for maybe_fix_fields_with_invalid_field_type() were corrupted in particular, all fields would be converted to text type.

Related GitHub issue(s)

Slack Report: https://podswp.slack.com/archives/C02SVLHQF/p1785336123838039?thread_ts=1785276302.714959&cid=C02SVLHQF

Testing instructions

Create some Pods. Add one of these filters then attempt a repair:

add_filter(
    'pods_whatsit_storage_post_type_find_args',
    function( $post_args ) {
        unset( $post_args['meta_query'] );
        return $post_args;
    },
    10,
    1
);

add_filter(
    'posts_pre_query',
    function( $posts, $query ) {
        if ( in_array( $query->get('post_type'), ['_pods_group', '_pods_field' ] ) ) {
            return [];
        }
        return $posts;
    },
    10,
    2
);

Run wp pods tools flush-cache after adding the filters... Post_Type::find() caches results (correct or incorrect) to a one-week transient.

Changelog text for these changes

Repair Tool: Protect and notify of potential plugin conflicts.

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).

There is a unit test... there was also an environment setup with scripts / WP CLI etc, not included...