[Pipeline] Ensure buildconfig yaml matches dev builds

Problem Description

During the 7.1.0CRx builds there where a number of build configs that where no longer "valid" for a number of reasons

• The component was no longer built as part of the pipeline but stuck at a version (already built)
• A new component had been added to the dev pipeline but not to the build configuration yaml required by the PiG tooling

Proposed Solution

• Ensure the number of pipeline components matches that of the yaml file

DoD

• It is no longer possible to create a yaml file that is affected by extra or missing components