Harden & optimize jira usage data

Problem

Currently in Usage Ping there are ~400 usage ping counters with varying implementations, this causes stability issues and in some causes an uncaught error can cause the entire usage ping to fail.

jira_usage is one of the usage ping counters that has a custom implementation.

Proposal

Rework the jira_usage counter with batch counting

Result

A more robust usage ping without single points of failure