Speed up RepositoryVersion saves on add/remove content

[gerrod3]

Was asking sol to take a look at our RepoContent/content_ids problem and it pointed this out. Postgres can't optimize the update to be on the HOT path since the indexes become targets without specifying the fields, or so the AI says. Can't hurt

Assisted-by: gpt-5.6-sol

📜 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

[patchback]

Backport to 3.85: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.85/66ea16ce236bce27f6a2088dedab2d98096c2ef0/pr-8086

Backported as #8092

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

[patchback]

Backport to 3.117: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.117/66ea16ce236bce27f6a2088dedab2d98096c2ef0/pr-8086

Backported as #8093

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

[patchback]

Backport to 3.105: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.105/66ea16ce236bce27f6a2088dedab2d98096c2ef0/pr-8086

Backported as #8094

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