Add EXTRA_INFO to profiling metrics

[wmTJc9IK0Q]

The EXTRA_INFO "metric" is not returned by default from duckdb. This adds it explicitly to each info node.

This includes info such as which table the operator was on, which columns were projections, etc.

[taniabogatsch]

Hi @wmTJc9IK0Q - I've looked into this and I think it would be cleaner to fix this on the C++ side - in the profiler, we should move extra_info into metrics. There's actually a FIXME in the C++ code already for this.

Would you be open to PR this to duckdb/duckdb and ping me on the PR? Otherwise, I can see if I can find the time (not sure when).

class ProfilingInfo {
public:
	//! Enabling a metric adds it to this set.
	profiler_settings_t settings;
	//! This set contains the expanded to-be-collected metrics, which can differ from 'settings'.
	profiler_settings_t expanded_settings;
	//! Contains all enabled metrics.
	profiler_metrics_t metrics;
	//! Additional metrics.
	// FIXME: move to metrics.
	InsertionOrderPreservingMap<string> extra_info;

[wmTJc9IK0Q]

Closing in favor of duckdb/duckdb#19124