Handle incomplete profile updates when intial update comes from a breaking change

[vladbarosan]

1. Commit A removes a type from an API version so its a breaking change. Profile is also updated as part of that.

2. Commit B comes and adds a new API version which also doesn't have the type that was removed in Commit A. This is a new api version so not a breaking change. The profile is updated to point to this new API version.

3. WE want to release a minor version. We dont pick up A, but we pick up B.

=> Problem is now after the B cherry pick, the removed type is still present since it was removed in A but we didn't pickup A.

[vladbarosan]

Right now a workaround is just to ignore the profiles while the picker does the cherry picking and regenerate the profiles after the picker is done.

[vladbarosan]

@jhendrixMSFT can we document the regeneration of profiles after the picker runs for the minor version updates ?

[vladbarosan]

Updated the wiki to reflect the additional step needed