Meta should include information about the view

Thanks for this patch! I needed the pager info in the output and this patch adds just that plus some more useful data.

Tests should be fixed however and there should be some new tests added for the new output.

There is already a good amount of this information available from the `view--view` resource, so it's best not to duplicate work too much.

The biggest issue with the `view--view` resource is that it contains too much unfilterable data, and returns all displays. I think it would be better to concentrate on improvements in that area and then using the relationship from this resource to get that data as required.

Then what do you propose? The pager information is loaded directly from the view itself, so there's hardly any code duplication. A pager is often essential for a view and I think it actually shouldn't take any extra work for it to be added to the API resource.

Glad to see others talking about - our use case would be to know what exposed filters exist on the view and what vocabularies they reference in order to programmatically build those exposed filters on the front end, rather than hardcoding.

I can get this information from the `view--view` like you say, but it would be pretty slick the metadata of the view was available alongside the data.

Noticed that the count is missing after the patch. Tweaked #4 ✨ Meta should include information about the view Needs work a little bit.