common name based client side filter for tables

In Horizon tables, most of the tables have the name based client side filter.
In each table, the filter action class is written individually.
but all the filter action class uses same logic and code.
just the name of the class and argument name is differs.

so we can have one generic filter action for name based filter in a common place, which will reduce the code duplication.
In horizon/tables/action.py is the right place to have the filter action class.