Platform: Refine the definition for an issues query endpoint

As discussed initially during the query API implementation meeting, we should refine what should be the core functionality offered by a issues endpoint.

We have discussed use cases like:

• total issue count
• issues created in a time range
• issues closed in a time range
• lead time for issues
• (all of the above filterable for a hierarchy (groups, projects, namespace))