Update usage information metrics for v2024.3

[matthew-white]

Metrics to add

• How many offline updates have been force-processed?
  • Should this include an offline update force-processed before the offline create? I.e., an offline update applied as a create?
    • Matt thinks ideally it would.
  • Moved from Update usage information metrics for v2024.2 #653
• How long does it take for an entire branch to be processed? Specifically: what is the max amount of time between when the first submission for a branch is received and when the last submission is processed?
  • Exclude branches where one of the updates was force-processed. We're more interested in the more normal case where a submission is put in the backlog just long enough for updates to be processed in the correct order. In other words, we expect the max amount of time to be less than 5 days (hopefully much less!).
  • Moved from Update usage information metrics for v2024.2 #653
• How many form definitions are XML-only and are not associated with an XLSForm?
  • When managed encryption is enabled for a project, Central will autogenerate new XML-only form definitions. It's a bug that XLSForms aren't carried forward (#729), but we don't want the bug to affect this metric. It'd be OK just to exclude all encrypted forms.
  • We may end up double-counting some autogenerated form definitions, e.g., if there's an XML-only form definition, and then we create a new version of it as part of (#692). In that case, the user only uploaded a single XML-only form definition even though their database says that there are two. I think that level of double-counting is OK though.

Metrics to remove

No metrics to remove (yet).

Checklist

• Update the form version string in the Backend config.
• Publish the new form version on data.getodk.cloud.
• Update the usage report in Frontend.