To allow the UI to provide a selection of attributes to create filters with, the UI currently creates a collection of filters based on scope and tracks their popularity across the devices the UI retrieved. For larger scales the devices shown in the UI might no longer represent a significant subset of the available attributes - so we have to obtain those from the backend to ease filter creation.
Due to previous user communications we know that the inventory attribute list might get quite long and is for that reason appreciated (to prevent typos)... still getting a subset with the most popular attributes (ordered by popularity or with the popularity) should be enough

acceptance criteria:

• provide an endpoint that returns attributes by scope (identity, inventory, system etc.)