Support per-option value normalization

[alamb]

Is your feature request related to a problem or challenge?

on #11330 (comment), @ozankabak says

We would like to have key-level control on what normalization means for config options, built-in and extension.

Describe the solution you'd like

Allow users of DataFusion to

1. Provide a new set of ConfigOptions (not in DataFusion) that have custom normalization rules
2. Avoid normalization on some of the built in configs?

Describe alternatives you've considered

The code from @berkaysynnada in synnada-ai@341b484 I think seems to show a way to add an annotation to a built in config setting value that controls how it will be normalized.

Additional context

This is a follow on to #11330 where we implemented all-or-nothing value normalization