Show applied filter

[kirya-dev]

Subject

Change the UX-behavior to stop hidding default filter and considering them as normal filters.

Closes #6217.
Closes #6137.
Closes #5745.

Changelog

## Changed:
- Stop to hide default filters in order to provide a more natural UX-behavior.

## Deprecate
- Abstract:: isDefaultFilter method.

[VincentLanglet]

@kirya-dev Test are failing because of the deprecation.

You have to add a @legacy annotation, a @expectDepraction deprecationMessage annotation and a NEXT_MAJOR: Remove this test comment , like it's done for some other test.

[kirya-dev]

You have to add a @legacy annotation, a @expectDepraction deprecationMessage annotation and a NEXT_MAJOR: Remove this test comment , like it's done for some other test.

Hmm. Test required for check default logic.. Test has others assert not related with isDefaultFilter

[jordisala1991]

The changelog is not well formed.

It will be nice to have some screenshots about before and after.

Ad it would be nice if you explain what is the alternative to setting default filters now. Bonus point if you add it to the deprecation message

[kirya-dev]

Ad it would be nice if you explain what is the alternative to setting default filters now

Configure default filter was not change

[VincentLanglet]

It will be nice to have some screenshots about before and after.

Before, you see nothing

But the filter was active

And you couldn't know the value applied.

Now, it's more natural

And it would be nice if you explain what is the alternative to setting default filters now. Bonus point if you add it to the deprecation message

You can still set default filter using the configureDefaultFilterValues method.
But if you're doing so, the filter will be displayed.
It's more user friendly to see how your list is filtered.

I you really want a hidden filter, you should rely on the configureQuery.

[VincentLanglet]

Thanks !