Send package versions as bundle metadata

[yunakim714]

Description

One of the main goals of the Bundle Metadata Upload work for the CC SteelArc team is to gather information on the packages and versions that constitute our customers' projects.
Utilizing the project's package.json, we will upload the dependencies and devDependencies as part of the bundle_metadata field of the Bundle model

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• Utilizing the preexisting getProjectPkg() function, access the package.json's dependencies and devDependencies fields
• Add this data to ssr_parameters

How to Test-Drive This PR

• Navigate to the related PR in portal_app and checkout the branch
• Using a local PWA Kit project, push a bundle running Cloud local from the project root
  ... pwa-kit-dev.js push -m "Test bundle_metadata is sending" --cloud-origin http://cloud-dev.mobify.com:8000
• Using SQL queries or otherwise, validate that the bundle_metadata field of the pushed bundle is populated with the project dependencies and versions in the following format:
  bundle_metadata: { "dependencies": { "package_a": "1.0.0", "package_b": "2.0.0" } }

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[bfeister]

@yunakim714 will there be a follow-up PR for ccExtensibility.overridesDir fs read + push to this payload?

[yunakim714]

@bfeister Yup! This PR is focused on sending just the package versions

[bfeister]

Just going to officially say that I'll need more convincing that it's ok to lower test coverage, we'll discuss in person