Newly deployed overcloud nodes don't get the latest patches applied

Issue

• When a new overcloud stack is deployed and its nodes are registered to Satellite, they don't automatically receive the latest packages available on the content view and lifecycle environment combination
• When nodes are added to an existing overcloud stack, they don't automatically receive the latest packages available on the content view and lifecycle environment combination at registration time, which results in mismatching errata between the existing and new hosts of the same overcloud
• New overcloud nodes are displayed with an "Errata" status of "Security errata applicable" on Satellite due to erratas pending to be applied