Add module defines to the per-platform generated props file so VS knows which ones are enabled.

[shana]

The modules_enabled.gen.h header containing the defines for the enabled modules is only generated on build, not during VS project generation, and it only reflects the list of modules enabled for the target and platform that was built most recently. That means that when you generate a project the first time, any code inside #ifdef MODULE_XXX_ENABLED will be shown as disabled, even if that module is actually enabled in the build, since the header doesn't exist yet. Additionally, if you generate the VS project with multiple targets and platforms, code inside MODULE_XXX_ENABLED conditions won't show up properly if the selected VS configuration doesn't match the most recent build target+platform combo, since the header only reflects the modules enabled on the latest build configuration.

This adds those defines to the VSHINT_DEFINES array, which goes into the NMakePreprocessorDefinitions property of per-platform generated props file that the project includes. This way, VS will have a better idea of the defines that are available and wil be able to render more better.

It's not a 100% accurate solution, because the generated header is still loaded and the list in it might not match the currently selected VS configuration. But, at least this guarantees that all modules that are enabled in the currently selected VS configuration will have their defines available to VS, making the code view more accurate.

/cc @akien-mga @Repiteo

[shana]

Note: the force-pushes here are just me rebasing on the newest master, I was behind in my local history and CI doesn't like building stuff that old, apparently.

[akien-mga]

The rationale makes sense to me and the change is pretty straightforward.

[Repiteo]

Thanks!