Global preprocessor definitions overwrite current preset preprocessor definition

When both the global ini and the preset ini have a preprocessor definition, the global one takes precedence, even though the UI suggests the opposite is true (when viewing preprocessor definitions for a shader, the value shown will be the preset one if there is a preset and global definition, even though the global one is the one actually in effect). This can be easily tested using RESHADE_DEPTH_INPUT_IS_REVERSED (or UPSIDE_DOWN) - if you have it set globally to 0, enabling displaydepth will show no difference if you add a preset definition for it to be 1.