Suggest workflow states based on low cycle times from other instances via usage ping

• With &364, teams will have custom workflows.
• With &505, we will show cycle times to teams.

We should aggregate those cycle times via the usage ping. And so we can know which workflows have very good cycle times. We can then push these as suggestions back at users themselves, when they create their own custom workflows.

There's a lot possibilities we can consider here to analyze how teams are working, and suggest helpful best practices / processes back to the users themselves.

This is a great idea suggested by @jmay1