Java: Assume normal termination in post-dominance.

[aschackmull]

This is a followup for #19885, which made this possible.

The concept of post-dominance may either assume normal termination of a callable, or try to account for exceptions. This PR switches Java to the former, which is in line with the shared CFG library. Indeed, trying to account for exceptions in post-dominance usually isn't what's desired, and it's also somewhat meaningless, since many potential exception edges are elided in the CFG if there's no enclosing try-block. As such, I'll consider this to be a bug-fix (and a somewhat minor one given that post-dominance is only rarely used).

[Copilot]

Pull Request Overview

This PR modifies the post-dominance calculation in Java's control flow analysis to assume normal termination rather than accounting for exceptions. The change aligns Java's behavior with the shared CFG library and addresses cases where exception handling in post-dominance analysis can be meaningless due to elided exception edges in the CFG.

• Updates post-dominance exit node definition to only consider normal exit nodes
• Excludes exceptional exit paths from post-dominance calculations

[aschackmull]

I've started dca with the only two queries using post-dominance: java/lazy-initialization (LazyInitStaticField.ql), java/improper-webview-certificate-validation (ImproperWebViewCertificateValidation.ql)