Add CollisionCount to StatefulSetStatus for collision avoidance

[liyinan926]

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug

What happened:
The Deployment controller uses the field CollisionCount as a collision avoidance mechanism when it needs to create name for the newest ReplicaSet. Similarly, the DaemonSet controller uses CollisionCount as a collision avoidance mechanism when it needs to create name for the newest ControllerRevision. Like the DaemonSet controller, the StatefulSet controller also creates ControllerRevision, but does not use CollisionCount for collision avoidance.

What you expected to happen:
The field CollisionCount should be added to StatefulSetStatus and used for collision avoidance like how the DaemonSet controller uses the field when creating name for the newest ControllerRevision.

How to reproduce it (as minimally and precisely as possible):
N/A.

Anything else we need to know?:
N/A.

Environment: N/A

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration**:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[k8s-github-robot]

@liyinan926
There are no sig labels on this issue. Please add a sig label by:

1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
   e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

2. specifying the label manually: /sig <label>
   e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. You can find the group list here and label list here.
The <group-suffix> in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

[liyinan926]

/sig apps

[liyinan926]

/assign @liyinan926