meson: fix undefined behavior with cdata.set10

This function has never taken a number, only a boolean. Due to leaky
python implementation details, it cast literally anything to bool
regardless, including somewhat common accidental usage of numbers. This
now prints an unavoidable deprecation notice stating that it may be
removed at any time.

Fix this to use what was always intended -- .set(), as used a few lines
down for another number.

Author: eli-schwartz

src/meson.build

@@ -7,10 +7,10 @@ config_cfg.set('INTEL_DRIVER_MICRO_VERSION', intel_vaapi_driver_micro_version)
 config_cfg.set('INTEL_DRIVER_PRE_VERSION', intel_vaapi_driver_pre_version)
 config_cfg.set10('HAVE_HYBRID_CODEC', get_option('enable_hybrid_codec'))
 if WITH_X11
-  config_cfg.set10('HAVE_VA_X11', 1)
+  config_cfg.set('HAVE_VA_X11', 1)
 endif
 if WITH_WAYLAND
-  config_cfg.set10('HAVE_VA_WAYLAND', 1)
+  config_cfg.set('HAVE_VA_WAYLAND', 1)
 endif
 if cc.has_function('log2f')
   config_cfg.set('HAVE_LOG2F', 1)