Improve Get-WinEvent -ListLog exception handling

[MartinGC94]

PR Summary

This PR improves the error handling for Get-WinEvent -ListLog by adding a dedicated catch block for UnauthorizedAccessException exceptions and preventing an incorrect error message about not finding the specified log from showing up if the event log was found, but was inaccessible. See this before and after for the UX
Before:

PS C:\> Get-WinEvent -ListLog security
Get-WinEvent: To access the 'Security' log start PowerShell with elevated user rights.  Error: Attempted to perform an unauthorized operation.
Get-WinEvent: There is not an event log on the localhost computer that matches "security".
PS C:\>

After:

PS C:\> Get-WinEvent -listlog security
Get-WinEvent: Access denied for log: 'Security'.
  Recommendation: Launch PowerShell with elevated user rights.
PS C:\>

WriteObject was also moved outside of the try-catch to fix an issue where the PipelineStoppedException exception was being caught, which prevented Select -First X from working.

I haven't added any tests because I don't see what I'd need to test to avoid regressions here.

PR Context

Fixes: #27390

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. If this PR is a work in progress, please open this as a Draft Pull Request and mark it as Ready to Review when it is ready to merge.
• 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

[Copilot]

Pull request overview

This PR improves Get-WinEvent -ListLog error handling by distinguishing access-denied failures from “log not found” scenarios and by avoiding catching PipelineStoppedException during output, improving UX and pipeline behavior.

Changes:

• Add dedicated handling for UnauthorizedAccessException to emit a permission-denied error with a recommended action.
• Move WriteObject outside the try/catch so Select-Object -First can stop the pipeline cleanly.
• Add new localized resource strings for the new error message and recommendation text.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx	Adds new resource strings used for access-denied messaging and elevation recommendation.
src/Microsoft.PowerShell.Commands.Diagnostics/GetEventCommand.cs	Updates ProcessListLog() to catch access-denied separately and avoid catching pipeline-stop exceptions during output.

[MartinGC94]

Certain log types are skipped so this cannot be moved to an earlier point.

[MartinGC94]

But what is the text file used for?

[daxian-dbw]

LGTM. Thanks @MartinGC94!