Name change `broken_hard_limits_for` -> `violated_hard_limits_for`

[seattlecyclist]

I would like to suggest a method name change.

I found the naming of broken_hard_limits_for confusing. I could not understand what was "broken" about these set of limits. I believe the intent of this methods is to get limits that have been violated, or infringed upon. If this is the case I would like to propose a change from broken_hard_limits_for to violated_hard_limits_for.

IMHO it more clearly speaks to the intent.

[jwright]

@seattlecyclist I am open to this as I don't have strong feels either way. I am wondering how you feel now that it has been a few weeks since working with it.

I ask because there is also broken_soft_limits_for as well now, which would become violated_soft_limits_for and I was wondering if you feel it is still clearer.