Follow best practice and require process rather than use global (#595)

https://nodejs.org/dist/latest-v16.x/docs/api/process.html#process
> The process object provides information about, and control over, the current Node.js process. While it is available as a global, it is recommended to explicitly access it via require or import:

Author: abetomo

bin/node-lambda

@@ -3,6 +3,7 @@
 'use strict'
 
 require('dotenv').config()
+const process = require('process')
 const path = require('path')
 
 const lambda = require(path.join(__dirname, '..', 'lib', 'main.js'))

lib/main.js

@@ -1,5 +1,6 @@
 'use strict'
 
+const process = require('process')
 const path = require('path')
 const os = require('os')
 const aws = require(path.join(__dirname, 'aws'))

lib/s3_deploy.js

@@ -1,5 +1,6 @@
 'use strict'
 
+const process = require('process')
 const crypto = require('crypto')
 // https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#createBucket-property
 const S3_LOCATION_POSSIBLE_VALUES = [

test/main.js

@@ -1,5 +1,6 @@
 'use strict'
 
+const process = require('process')
 const path = require('path')
 const os = require('os')
 const fs = require('fs-extra')

test/node-lambda.js

@@ -1,6 +1,7 @@
 'use strict'
 
 const assert = require('chai').assert
+const process = require('process')
 const path = require('path')
 const fs = require('fs-extra')
 const spawn = require('child_process').spawn

test/s3_deploy.js

@@ -1,6 +1,7 @@
 'use strict'
 
 const { assert } = require('chai')
+const process = require('process')
 const path = require('path')
 const aws = require('aws-sdk-mock')
 aws.setSDK(path.resolve('node_modules/aws-sdk'))