Description of problem:
Bulk package profile update calls right after client registration causes failure of subsequent client registrations to Satellite.

Version-Release number of selected component (if applicable):
Satellite 6.2.11

How reproducible:
Always

Steps to Reproduce:
1. Register multiple clients (5 to 10) to Satellite6 concurrently - with each of them running puppet modules to pull content from Satellite6 right after registration

Actual results:
In the customer environment, there were 40 package profile updates per host right after client registration which slowed down Satellite and made subsequent client registrations to fail.  Note that the subscription-manager on the client have a 60 sec default timeout which is not configurable at this time.

Expected results:
Reduce the package profile update processing time so cases like this (40 package profile updates per host right after registration) does not consume lot of Satellite resources and delay registration of subsequent clients.

Additional info:
Package profile processing logic needs to be improved to make it faster
- During the investigation, it was found that katello_installed_packages need to be indexed as this table might grow very quickly
- Need to de-duplicate the data in the table