Description: Katello 4.13 , 4.14 use pulpcore 3.49. We have an upstream user running into some task performance degradation following the upgrade owing to task queries against fields that are not indexed in 3.49. The new indices landed in 3.54 :https://github.com/pulp/pulpcore/pull/5368/

We need to look at back-porting this to Katello 4.13 or 4.14 which is going to be what goes into Sat 6.16. Wondering if the packaging team might be able to do this or if we can create these indices on pulpcore db tables externally via the installer outside of pulp migration which will land in 3.54.  This request comes from findings here: https://community.theforeman.org/t/publish-and-promote-slow-with-3-11-4-13/39040 

How reproducible:

This should be reproducible in form of pulp task performance degradation with a lot of tasks in the db.

Is this issue a regression from an earlier version:

Yes

Steps to Reproduce:

1. 

2.

3.

Actual behavior:
[Describe the issue in detail, including what is happening and where]

Expected behavior:
[Describe what should be happening instead]

Business Impact / Additional info:

Possible workaround: Set the setting completed_pulp_task_protection_days to a very low value like 7 or so and run orphan cleanup to purge tasks completed before 7 days. That should reduce the number of tasks in the db limiting the performance impact on new tasks.