get_total_objects_for_query_from_db(): bail if we have any limits set

[rebeccahum]

Description of the Change

Slight continuation from #2571. We should bail if ep_indexing_lower_limit_object_id or ep_indexing_upper_limit_object_id is set since we're only looking for the total count from the DB and there's no way to determine that based on the object ID limits.

Alternate Designs

N/A.

Possible Drawbacks

It will return a 0, so doesn't exactly fix the initial problem if we run into that with the limit ids.

Verification Process

On a yuge site where it kills the found_posts in get_total_objects_for_query(), pass in --upper-limit-object-id and expect it to return 0 instead of an inaccurate number.

Checklist:

• I have read the CONTRIBUTING document.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests passed.

Changelog Entry

Fixed: Do not count posts in get_total_objects_for_query_from_db() if any object limit IDs are passed in

Credits

Props @rebeccahum