Rename browse controller to queries controller

[AntonKhorev]

The only thing left in browse controller was the query sidebar.

[tomhughes]

I fine with this in principle, I just wonder what the right name is and I'm not sure that QueriesController is it.

I started off thinking it should be singular as QueryController which I realise doesn't fit with resourceful naming from using a resource route but then maybe that's the point, that it's not managing a set of resources so shouldn't be a resourceful route?

Then I thought maybe it should be FeaturesController because features are the resource that is being queried? At least that's how the UI describes it...

[AntonKhorev]

What's wrong with QueriesController? When you see this controller name, you know it handles either /queries/:id or /query paths. FeaturesController instead you'll have to investigate because there's no "features" route.

If we change the path however... I'm thinking about combining query features with map key. There's a proposal to change the map key icon, but I don't think users will find it significantly more clear. The query button might open the sidebar right away and show map key there. And also sort out #3819, #3833 and #3709.