build: use the same python executable to run configure and gyp

Otherwise we would end up using python 2 to run actions in the gyp
config if that's the system default.

configure.py

@@ -1925,6 +1925,7 @@ def make_bin_override():
 
 # Forward OSS-Fuzz settings
 output['variables']['ossfuzz'] = b(options.ossfuzz)
+output['variables']['python_exec'] = sys.executable
 
 # variables should be a root level element,
 # move everything else to target_defaults

node.gyp

@@ -27,6 +27,7 @@
     'node_lib_target_name%': 'libnode',
     'node_intermediate_lib_type%': 'static_library',
     'node_builtin_modules_path%': '',
+    'python_exec': 'python',
     # We list the deps/ files out instead of globbing them in js2c.py since we
     # only include a subset of all the files under these directories.
     # The lengths of their file names combined should not exceed the
@@ -784,13 +785,14 @@
             {
               'action_name': 'mkssldef',
               'inputs': [
+                '<(python_exec)',
                 'deps/openssl/openssl/util/libcrypto.num',
                 'deps/openssl/openssl/util/libssl.num',
               ],
               'outputs': ['<(SHARED_INTERMEDIATE_DIR)/openssl.def'],
               'process_outputs_as_sources': 1,
               'action': [
-                'python',
+                '<(python_exec)',
                 'tools/mkssldef.py',
                 '<@(mkssldef_flags)',
                 '-o',
@@ -816,7 +818,7 @@
             '<(SHARED_INTERMEDIATE_DIR)/node_javascript.cc',
           ],
           'action': [
-            'python',
+            '<(python_exec)',
             'tools/js2c.py',
             '--directory',
             'lib',