Disable cost saving functionality

[amahussein]

Signed-off-by: Ahmed Hussein (amahussein) [email protected]

Fixes #1217

• this change adds a configuration flag that force disabling the cost savings
• even when a cluster or platform is part of teh argument, the Q tool output won't include any data related to costs.
• this is temp solution to disable the cost-savings. Later, there will be other issues to cleanup the dead-code

The full list of tasks is tracked in #1221

[parthosa]

Thanks @amahussein. LGTME. I have few questions:

1. What are the plans for the argument --filter_apps savings? It would currently throw an exception for the following CMD:

spark_rapids qualification --platform databricks-aws  --eventlogs $EVENTLOG_PATH  --tools_jar $SPARK_RAPIDS_TOOLS_JAR --filter_apps savings --cluster ~/Work/cluster/databricks-aws/databricks-aws-cpu.json

2 Do we plan to remove 'SAVINGS' word from the console output when we clean up the csv files columns?

    - Summarized savings and speedups CSV report: /Users/psarthi/Work/tools-run/qual_20240723194339_11E13C20/qualification_summary.csv
    - Full savings and speedups CSV report: /Users/psarthi/Work/tools-run/qual_20240723194339_11E13C20/qualification_summary_full.csv

[amahussein]

Thanks @amahussein. LGTME. I have few questions:

1. What are the plans for the argument `--filter_apps savings`? It would currently throw an exception for the following CMD:

spark_rapids qualification --platform databricks-aws  --eventlogs $EVENTLOG_PATH  --tools_jar $SPARK_RAPIDS_TOOLS_JAR --filter_apps savings --cluster ~/Work/cluster/databricks-aws/databricks-aws-cpu.json

2 Do we plan to remove 'SAVINGS' word from the console output when we clean up the csv files columns?

    - Summarized savings and speedups CSV report: /Users/psarthi/Work/tools-run/qual_20240723194339_11E13C20/qualification_summary.csv
    - Full savings and speedups CSV report: /Users/psarthi/Work/tools-run/qual_20240723194339_11E13C20/qualification_summary_full.csv

Yes, we need to remove arguments related to the cost-savings, and do all the other logistics.
However, this is going to be some sort of long process that includes cleaning up the code and refactoring.

The purpose of this PR is an immediate block to cancel Cost-savings.

• Since the cost savings are automatically generated when the cluster-information is provided,
• cost-savings does not match what the Tuning path is doing.
• The tuning generates output per-app, while cost savings generates output per-cluster.

[parthosa]

Thanks @amahussein. RIP cost savings.