Data driven scope buttons

[markwhiting]

• The scope buttons should show up based on the features in the project.
• We should have logic that works out the right way to aggregate rows depending on the selected scopes without extra data or hard coded controls
• We should handle situations where the list of scopes is too long to display, e.g. if someone looks at all papers so they get all scopes across our data (this is a design problem and can be split out as another issue if needed)