[data processing] Add filtering to tables

Summary
=======
In the data processing panels, there are several tables that can become rather lengthy. Given that, it is desireable to incorporate filtering.

Motivation
========
Viewing tables with large numbers of results, many of which may be inconsequential
to the goal of the user, is cumbersome for users to deal with. Allowing the user
to filter the results to only contain pertinent information is a much better
user experience.

Description
=========
As discussed at the Kilo summit, tables that need filtering applied:
Node group templates (by name, plugin, version)
Cluster templates (by name, plugin, version)
Clusters (by name)
Job execution (by name, job, cluster)
Jobs (by name)

UX
===
This was discussed at the Kilo summit. The UX for table filtering in data processing
will follow the same conventions that table filtering uses in other areas of the Horizon
UI.

Wireframes, Mocks, Videos and UI Markup
---------------------------------------------------------
N/A

Testing
======
Tests will be added to support the filtered table scenarios.

Outside Dependencies
==================
There are changes required to the Sahara client library as well as the Sahara service
itself in order to support filtering capabilities.

Here are the blueprints for those work items. They both need to be finished before
the Horizon change can be merged.

Sahara service: https://blueprints.launchpad.net/sahara/+spec/enable-result-filtering
Client library: https://blueprints.launchpad.net/python-saharaclient/+spec/enable-result-filtering

Requirements Update Required
========================
requirements.txt will need to be changed to increment the version of python-saharaclient (exact version number is currently unknown and will depend on timing) in order to pick up the changes to support query filtering.

Doc Impact
=========
N/A