The code in widenGEP has already been transitioned to only rely on
information provided by VPWidenGEPRecipe directly.
Moving the code directly to VPWidenGEPRecipe::execute completes
the transition for the recipe.
It provides the following advantages:
- Less indirection, easier to see what's going on.
- Removes accesses to fields of ILV.
- in particular ensures that no dependencies on
fields in ILV for GEP code generation are re-introduced.
Better keep both addMetadata() methods next to each other; the one left below is not more "protected" than this one, plus their documentations are linked - above refers to the "previous function" below.