PR Summary

This pull request includes several updates to the tools/cgmanifest.json file to upgrade NuGet package versions and adds a new function to tools/findMissingNotices.ps1 to handle semantic version conversion. Below are the most important changes:

NuGet Package Version Updates:

• Updated Json.More.Net from 2.0.0 to 2.0.1.2 (tools/cgmanifest.json).
• Updated JsonPointer.Net from 4.0.0 to 5.0.0 (tools/cgmanifest.json).
• Updated JsonSchema.Net from 6.0.2 to 7.0.1 (tools/cgmanifest.json).
• Updated Markdig.Signed from 0.34.0 to 0.37.0 (tools/cgmanifest.json).
• Updated Microsoft.Bcl.AsyncInterfaces from 5.0.0 to 8.0.0 (tools/cgmanifest.json).

Semantic Version Handling:

• Added ConvertTo-SemVer function to handle non-standard semantic versions (tools/findMissingNotices.ps1).
• Modified Get-NuGetPublicVersion function to use the new ConvertTo-SemVer function for version conversion (tools/findMissingNotices.ps1).

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    - [ ] Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: