Add 7.4.9 changelog

[jshigetomi]

PR Summary

This pull request includes updates to the CHANGELOG/7.4.md file, documenting the changes for the 7.4.9 release. This release is internal only and includes several improvements and updates.

Tools:

• Check GH token availability for Get-Changelog ([release/v7.4]Check GH token availability for Get-Changelog #25156)

Build and Packaging Improvements:

• Update .NET SDK to 8.0.407
• Update branch for release ([release/v7.4] Update branch for release  #25101)
• Only build Linux for packaging changes ([release/v7.4]Only build Linux for packaging changes #25161)
• Skip additional packages when generating component manifest ([release/v7.4]Skip additional packages when generating component manifest #25160)
• Remove Az module installs and AzureRM uninstalls in pipeline ([release/v7.4]Remove Az module installs and AzureRM uninstalls in pipeline #25157)
• Add GitHub Actions workflow to verify PR labels ([release/v7.4]Add GitHub Actions workflow to verify PR labels #25158)
• Update security extensions ([release/v7.4]Update security extensions #25099)
• Make Component Manifest Updater use neutral target in addition to RID target ([release/v7.4]Make Component Manifest Updater use neutral target in addition to RID target #25100)

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:

[jshigetomi]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[microsoft-github-policy-service]

📣 Hey @jshigetomi, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms