In case the recipe uses its own package_id() and compatible packages
are generated automatically (e.g. Visual Studio vs msvc), then the compatible
packages will use wrong 'base' info set for the compatible package id
generation.

In case the recipe's own package_id() erases a few options / settings,
the compatible packages will not know about it, as those are generated prior
the recipe's package_id() is being called.

The change makes sure that first the recipe's package_id() is called, then
the compatible packages are generated, so that they pick up the updated
info set.

In case a custom package_id() erased some of the compiler settings for
'msvc', a 'Visual Studio' equivalent should be created that also
doesn't have the (possibly) erased elements.