[FEA] Add support for driver log as input to profiler to generate unsupported operations detailed report

[mattahrens]

The event log does not have detailed enough information to explain why certain operators (execs/expressions) did not run on GPU for a Spark RAPIDS application. We want to extend the profiler tool to accept a driver log as input and generate a detailed unsupported operations report.

Input: --driverlog file path
Output

• Name: unsupported_ops.csv
• Fields: operator, fallback_reason

[mattahrens]

@viadea: let me know if the requirements are acceptable for the profiler accepting driver log as input and generating an unsupported operations report.

[viadea]

That looks good to me.