Add distinction between "info" and "fallback" messages

[andygrove]

What is the problem the feature request solves?

Comet currently uses "withInfo" to add information messages to the plan and also uses it to indicate that the operator/expression should fall back to Spark.

It would be nice to have the ability to tag plans with purely informational messages that do not indicate that the plan should fall back.

Describe the potential solution

No response

Additional context

No response

[andygrove]

This is more important now that we have codegen dispatch. if we pick the jvm version rather than native, we should let user know there is a faster option that can be enabled.