[FEA] Qualification/Profiling Tool: Store spark runtime for different application type

[parthosa]

As we add support for various runtimes (e.g., Spark, Photon, and future support for Velox), we should store the Spark Runtime information for each application.

This will be consumed by the Python CLI and QualX to make decisions based on the runtime type.

[tgravescs]

It would be good to specify in the description which tool(s) this feature is being added to - profiling or qualification.

If an application uses multiple in the future - like Velox and Spark Rapids I guess we can make a VELOX_AND_SPARK_RAPIDS type indicator, otherwise it may have been good to make this a list. Its not totally clear to me what all this is used for to decide which is better.

Is there a qualx issue this can be linked to, to understand the usage?

[parthosa]

It would be good to specify in the description which tool(s) this feature is being added to - profiling or qualification.

Updated the description to include the Tool

If an application uses multiple in the future - like Velox and Spark Rapids I guess we can make a VELOX_AND_SPARK_RAPIDS

Yes, we will have to extend the enums if an app uses multiple runtime

Is there a qualx issue this can be linked to, to understand the usage?

QualX Usage:

• Add qualx support for platform runtime variants (DB AWS) #1417
• Code Block - Link

Python CLI Usage

• Add qualification support for Photon jobs in the Python Tool #1409
• Code Block - Link