Pass same options to table as visualisation

Getting the valueAttr from the model was not reliable because it may not exist there and be defaulted for some modules.
Parameterise the periods for date-pickers

To prepare for extending the class for weekly journey date pickers.
Stop using `queryParams` method for journey collection

`queryParams` overwrites any params which are on the data-source model, so these can't be written to.

Instead provide default date ranges by setting the values on the collection data-source at initialisation, so they can then be subsequently overwritten (by date pickers)
Pass datepicker class as an option to module views

So that particular module types, in this case "journey" can use specfic date picker behaviour for their purposes.
Merge pull request #697 from alphagov/feature/journey-date-pickers

Feature/journey date pickers