Optimize provenance content query for integrity api

[gerrod3]

Found this with Sol analyzing the top SQL queries on Hosted Pulp, accidentally evaluating the entire content query before filtering it down anytime a user requested a providence object.

📜 Checklist

• Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
• A changelog entry or entries has been added for any significant changes
• Follows the Pulp policy on AI Usage
• (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 50 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: c54463ce-a41e-4e5c-8270-5fad6acb2152

📥 Commits

Reviewing files that changed from the base of the PR and between 5e5029e and 0c08c89.

📒 Files selected for processing (2)

• CHANGES/+integrity-db-query.bugfix
• pulp_python/app/pypi/views.py

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[patchback]

Backport to 3.36: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.36/f35abcf8691b5d2d9eb7ebf6dd0049e1f8128ac4/pr-1400

Backported as #1401

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.