Update CODEOWNERS

[adityapatwardhan]

Update code owners with new owners and remove some areas without owner

PR Summary

This pull request includes changes to the .github/CODEOWNERS file to update the ownership assignments for various areas of the project. The most important changes include reassigning ownership for security-related files, CI build configurations, and build-related files.

Ownership updates:

• src/System.Management.Automation/security/wldpNativeMethods.cs: Ownership updated to include @seeminglyscience.
• .github/workflows and .github/actions: Ownership assigned to @PowerShell/powershell-maintainers.
• src/System.Management.Automation/engine/remoting: Ownership updated to include @daxian-dbw and @TravisEz13.

CI and build-related updates:

• *.config, *.props, *.yml, *.csproj, build.*, tools/, and docker/: Ownership assigned to @PowerShell/powershell-maintainers.

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:

[TravisEz13]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[microsoft-github-policy-service]

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

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms