[Bug] Fix Yarn running state fallback

[hutiefang76]

What changes were proposed in this pull request

Issue Number: close #4356

When StreamPark falls back to Yarn after failing to get the task status from the Flink REST API, it currently reads Yarn finalStatus. For an application that is still in progress, Yarn usually reports finalStatus=UNDEFINED while the actual application state is in the state field, for example RUNNING.

This change resolves the Yarn application state by:

• using finalStatus when it maps to a known terminal result such as SUCCEEDED, FAILED, or KILLED
• falling back to Yarn state when finalStatus is not a known StreamPark state, so running applications can be updated as RUNNING instead of being skipped

Brief change log

• Add resolveYarnAppState for Yarn state/finalStatus conversion in FlinkAppHttpWatcher
• Use the resolver in both Yarn fallback paths
• Add unit coverage for finalStatus=UNDEFINED,state=RUNNING, terminal SUCCEEDED, and missing app info

Verifying this change

This change added tests and can be verified as follows:

• git diff --check -- streampark-console/streampark-console-service/src/main/java/org/apache/streampark/console/core/watcher/FlinkAppHttpWatcher.java streampark-console/streampark-console-service/src/test/java/org/apache/streampark/console/core/watcher/FlinkAppHttpWatcherTest.java
• JAVA_HOME=$(/usr/libexec/java_home -v 17) ./mvnw -pl streampark-console/streampark-console-service -am -Dtest=FlinkAppHttpWatcherTest -Dsurefire.failIfNoSpecifiedTests=false test

Does this pull request potentially affect one of the following parts

• Dependencies (does it add or upgrade a dependency): no

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud