bug fixes to make aws pr-test build work same as cicrcle ci

[dpatil-magento]

How to test - Fail conditions -

1. To test yarn install --frozen-lockfile || exit 1
   Change "babel-eslint": "~10.0.1" to "babel-eslint": "~15.0.1" and git Push then observe aws log.

2. To test yarn run build || exit 1
   packages/venia-concept/src/components/SearchBar/stories/searchBar.js make some compilation errors like remove ( and git Push then observe aws log

3. To test yarn workspace @magento/venia-concept run storybook:build || exit 1
   packages/venia-concept/src/components/SearchBar/stories/searchBar.js change import { SearchBar } from '../searchBar'; to import { SearchBar } from '../searchBar/adjshsf'; and git Push then observe aws log

4. To test yarn run danger packages/venia-concept/src/tests/example.spec.js change expect(true).toBe(true); to expect(true).toBe(false);

Pass Condition -
If there are no errors then "yarn run danger " should exit with status code 0

[magento-cicd2]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Devagouda Patil seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

[vercel]

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.

[coveralls]

Coverage remained the same at 77.164% when pulling 9871e35 on aws-pr-test-build-bugfix into 0d812ea on develop.

[sharkySharks]

This looks good 👍

[sharkySharks]

still looking good 👍

[sharkySharks]

👍