[HIGH] Bumping to 4.14.2-0

[compulim]

Description

After release of 4.14.1, we are bumping to 4.14.2-0.

Design

Specific Changes

• Update package.json and package-lock.json for 4.14.2-0
• Adding 4.14.1 to servicingPlan.json
  • It will be up to services team to enable it
• Update all samples to use [email protected]
  • Run npm install [email protected] on samples which use NPM version of Web Chat

• I have added tests and executed them locally
• I have updated CHANGELOG.md
• I have updated documentation

Review Checklist

This section is for contributors to review your work.

• Accessibility reviewed (tab order, content readability, alt text, color contrast)
• Browser and platform compatibilities reviewed
• CSS styles reviewed (minimal rules, no z-index)
• Documents reviewed (docs, samples, live demo)
• Internationalization reviewed (strings, unit formatting)
• package.json and package-lock.json reviewed
• Security reviewed (no data URIs, check for nonce leak)
• Tests reviewed (coverage, legitimacy)

[cwhitten]

@compulim I'm curious why this is adding 13k LOC

[compulim]

@compulim I'm curious why this is adding 13k LOC

All package-lock.json in this PR are for samples. They were pointing to 4.14.0 and now 4.14.1.

In 4.14.0 -> 4.14.1, we did a lot of package bumps (for security vulnerabilities). That's why we have so many changes in samples/.../package-lock.json. None of the package-lock.json are from production code.

TBH, better we should write a GitHub Actions that do this job in an automated way. I always worry about our package-lock.json pointing to a registry outside of NPMJS.