Change Request Metric Revision

The [Starter Viability Model](https://chaoss.community/?p=5608), talks about some of the reasons to care about change requests that aren't reflected in the actual [Change Request](https://github.com/chaoss/wg-evolution/blob/main/focus-areas/code-development-process-quality/change-requests.md) metric.

> Projects with very low count of change requests are unlikely to be keeping up with security updates – or with trends for development in their ecosystem. Change requests with high spikes of activity might also indicate that a project doesn’t provide sufficient checks to avoid unnecessary revisions/toil around the same feature.

I think we should tweak the Objective / Description to add these ideas, but I know we are in the process of reformatting our metrics using a new template, and I didn't want to interfere with that work. I'm happy to propose these changes if that would be helpful (if so, I just need to know where we landed on the new template) :)