ENHANCEMENT: Zipper is assuming all production dependencies needed; no dependency filter

[amp5208]

Use Cases:
Precondition:

• Nike-Inc/lambda-zipper dependency
• A GitHub repository that looks like this:

.
  ├── ...
  ├── lambda1/
  │   └── ...
  │   └── package.json
  ├── lambda2/
  │   └── ...
  │   └── package.json
  ├── nodejsReactUI/
  │   └── ...
  │   └── package.json
  ├── package.json

GIVEN a lambda component and handler within a product sub-directory (e.g., lambda1
AND another NodeJS component within another product sub-directory (e.g., lambda2 or nodejsReactUI)
AND a root package.json and individual component package.json definitions
WHEN I package lambda1 using the Nike-Inc/lambda-zipper tool
AND provide a whitelisted filter in the following pattern: [:alpha:].+($YOUR_FILTER_TEXT)[:alpha:].+
THEN lambda1 component is packaged using only the filtered production NodeJS dependencies
AND the lambda2 and nodejsReactUI components can be packed separately, with different filters
Post-condition: lambda2 and nodejsReactUI components are packed with a different filter

Problem Statement: As a Dev/Ops engineer, I want to be able to have an easy way to package my AWS Lambda code with different dependencies than my other product modules, even if the product is wholly housed in a single repository. This provides me value so that CI automation tools do not have to be custom configured to perform separate NPM install actions within sub folders, and ensures that AWS Lambda packages remain small.

Note: Issue will be resolved by including pre-filtering on production NPM dependencies at effecting this line of code:

lambda-zipper/src/zipper.js

Line 24 in 254af89

let npm = exec('npm ls --prod --parseable', { cwd: workingDir })