Qualification tool - Handle cancelled jobs and stages better and don't skip the app

[tgravescs]

Fixes #1032

I ran an event log through the qualification tool and it got labelled as not applicable because it had failed stages. Those failed stages though were cancelled by AQE runs.

We should take this into account in the qual tool.

The reasons in task show up as: Stage cancelled...
The stage failure reason shows: Job 243 cancelled

tool output:
24/05/23 10:00:26 WARN QualificationEventProcessor: SQL execution id 47 had failures, skipping
24/05/23 10:00:26 WARN QualificationEventProcessor: SQL execution id 125 had failures, skipping

This PR fixes that by looking for cancelled in the failure messages ignores those as failures.

I tested on customer event log and this is working. Need to put that event log into our integration tests.

[amahussein]

Thanks @tgravescs for putting the fix.
During refactoring the tools, I found that the profiler was adding treating failed jobs in a different way.

Shall we fix the two cod blocks to get the Q/P consistent? Or you prefer to file a separate issue?

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

Lines 61 to 63 in a6fdc86

	def hasFailed: Boolean = {
	sInfo.failureReason.isDefined
	}

For task failed, should we check for event.taskInfo.taskKilled in

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

Line 88 in a6fdc86

event.taskInfo.successful,

this is the code that loops on failed tasks.

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

Lines 98 to 101 in a6fdc86

	// Return a list of tasks that failed within all the stageAttempts
	def getAllFailedTasks: Iterable[TaskModel] = {
	getAllTasks(Some(!_.successful))
	}

[tgravescs]

they should be separate. when I looked briefly at the profiling tool, I know its outputting failed jobs to files. We still want to do that as that is how Spark is showing them. I didn't look at all the rollups though to see where it they are affected. Again a separate issue which I don't think is as important.

[amahussein]

LGTME