[DataGrid] Filter value are conserved when possible

[alexfauquette]

Fix #3188

The behavior

If column type changes, we try to keep the same operator (if available in the new column)
If the operator changes, we reset the filter Value if Input components are different.

Limitation

The singleSelect type is special because the input component is the same as the text input, but it behaves differently. That's why it has a specific case in column cahnge. Moreover, it implies to check if the value is available in the value options

[m4theushw]

We need a couple of test cases since the filtering is a critical part.

[m4theushw]

It's working correctly. My only comments are to improve the tests. We could add a test case using singleSelect since it does a bit of additional work to sanitize the options.

[alexfauquette]

I had to remove the sanitization for singleSelect because we have a test "should work if valueOptions is not provided". So if I make sanitization, it will be a kind of breaking change.

[m4theushw]

Removing the sanitization created one regression:

I had to remove the sanitization for singleSelect because we have a test "should work if valueOptions is not provided". So if I make sanitization, it will be a kind of breaking change.

This is test is meant to ensure that the grid won't crash if the valueOptions is undefined. Although, if it's defined and there's no corresponding value it can still be sanitized.

[m4theushw]

This can be removed.

[alexfauquette]

@m4theushw Nice catch this regression :)

I did not notice that the test was for the special case of undefined. I made it such that the sanitization is applied if the valueOptions is different from undefined, And adding tests, to prevent the regression you found

[m4theushw]

Just a small detail. For a brief moment, filterValueState will contain an invalid value if we don't return.

Suggested change

	applyValue({ ...item, value: itemValue });
	applyValue({ ...item, value: itemValue });
	return;