feat: expose comet metrics through Sparks external monitoring system

[coderfender]

Which issue does this PR close?

Closes #3712

Rationale for this change

1. We currently collect metrics and show while logging in comet. This PR is to essentially go a step further and wire the metrics out to be visualized in comet through tools like Grafana . As more users start using comet, these metrics would be helpful in understanding acceleration from comet standpoint. These are first Comet metrics exposed to Spark's external monitoring system and more would follow

The following metrics are exposed at the moment :

1. comet.operators.native
2. comet.operators.spark
3. comet.queries.planned
4. comet.transitions
5. comet.acceleration.ratio (acceleration : native / (native + spark)

What changes are included in this PR?

How are these changes tested?

[coderfender]

cc : @andygrove

[coderfender]

@wForget , Please take a look whenever you get a chance

[coderfender]

@wForget , I addressed code per your review comments. Please take a look whenever you get a chance. Thank you for the kind guidance

[wForget]

Suggested change

	val queriesBefore = CometSource.QUERIES_PLANNED.getCount
	spark.sparkContext.listenerBus.waitUntilEmpty()
	spark.sparkContext.listenerBus.waitUntilEmpty()
	val queriesBefore = CometSource.QUERIES_PLANNED.getCount

[wForget]

1. move sc.env.metricsSystem.registerSource(CometSource) into this method, and add a configuration to make this behavior configurable
2. Check if spark.sql.queryExecutionListeners is configured and merge it. You can refer to the implementation of registerCometSessionExtension method.