Release pipeline updates and package upgrades

[c-ryan-k]

Changes include:

• Pipelines
  • Removed default azure-pipelines.yml as it's just a wrapper for build-and-test-template.yml and github actions are currently running for PRs anyway.
  • Modified build/test and release pipelines to use npm ci to lock down dependency versioning for releases and testing.
  • Added component governance and SDL checks to release pipeline
  • Release pipeline overhauled for SDL compliance
  • Re-added MacOS DMG notarization step
  • Added suppressions file for credscan and updated tests
• Other changes
  • Package versioning updates for vulnerability updates

---

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Thank you for contributing to the Azure IoT Explorer!

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

• If introducing new functionality or modified behavior, are they backed by unit tests?
• Have all unit tests passed locally? (by running npm run test command)
• Have you updated the README.md with new screenshots if significant changes have been made?
• Have you update the package version if the current version in package.json is not higher than the version released?

[c-ryan-k]

Marking this as ready for review while I do some pipeline test runs to validate the new release pipeline end-to-end.