Adds filter for failed and non completed stages

[sayedbilalbari]

Fixes #1552

Currently we store the stageInfo using the stageModelManager class where we map incoming stage information during the following events -

1. doSparkListenerStageCompleted
   

   spark-rapids-tools/core/src/main/scala/org/apache/spark/sql/rapids/tool/EventProcessorBase.scala

   Line 475 in 1f037fa

   app.getOrCreateStage(event.stageInfo)

2. doSparkListenerStageSubmitted. -
   

   spark-rapids-tools/core/src/main/scala/org/apache/spark/sql/rapids/tool/EventProcessorBase.scala

   Line 464 in 1f037fa

   app.getOrCreateStage(event.stageInfo)

So a stage information is updated once when a stage is submitted and once during completion. A stageCompleted event comes for an attempt for a failed stage as well ( eg - there will be two stage Submitted and StageCompleted events for stage that fails on first attempt and succeeds on attempt 2)
Both those stageInfo objects are updated in the map
This PR adds extra filters to calculate aggregate metrics only for stages that have not failed and have completed successfully.

Changes -

1. Add a new method - getAllCompletedStages for filtering StageInfo objects on being successful and completed
2. Changes previous usages of getAllStages to getAllCompletedStages

Effects -

This change now ensures that all stage level aggregate metrics generated only take into account the successful ( not failed and completed ) ones