Standardize PodDescriber behavior to return NotFound errors consistently

[scaliby]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR unifies the error handling behavior of PodDescriber to match all other resource describers.

Currently, PodDescriber contains special-cased logic that attempts to fetch and print events for a deleted Pod, but only when triggered via a file (e.g., kubectl describe -f pod.yaml).

This creates an inconsistency:

• Standard Behavior: All other describers (and PodDescriber via direct name/selector) return a standard Error from server (NotFound) when the resource is missing.

• Inconsistent Behavior: PodDescriber via -f suppresses the error and attempts to recover events.

I have removed the fallback logic that attempts to print events for deleted pods. PodDescriber will now consistently return the standard "NotFound" error regardless of how the user queries the resource (-f, name, or --label-selector).

Benefits:

• Consistency: Aligns PodDescriber with the UX of the rest of the CLI.

• Code Simplification: This simplifies the upcoming refactor to support runtime.Object in ResourceDescriber (addressing kubectl describe suffers from N+1 query problem when falling back to prefix search, causing performance issues kubectl#1769). Removing this name/namespace-dependent logic now removes the need to port complex edge-case handling to the parent interface later.

$ kubectl delete service/my-service
service "my-service" deleted
$ kubectl delete pod/nginx-pod
pod "nginx-pod" deleted
$ kubectl describe service my-service
Error from server (NotFound): services "my-service" not found
$ kubectl describe -f service.yaml 
Error from server (NotFound): services "my-service" not found
$ kubectl describe pod nginx-pod
Error from server (NotFound): pods "nginx-pod" not found
$ kubectl describe -f pod.yaml 
- Pod 'nginx-pod': error 'pods "nginx-pod" not found', but found events.
- Events:
-   Type    Reason     Age   From                                   Message
-   ----    ------     ----  ----                                   -------
+ Error from server (NotFound): pods "nginx-pod" not found

Which issue(s) this PR is related to:

kubernetes/kubectl#1769

Does this PR introduce a user-facing change?

Remove event listing behavior when describing a removed pod from file.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: scaliby
Once this PR has been reviewed and has the lgtm label, please assign apelisse for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• staging/src/k8s.io/kubectl/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment