[Delivers #184624479] Fix trafgen getting stuck when bind cpu is set to value >=64

Trafgen was getting stuck when bind-cpu was set to a number >= 64, when the cluster node has more than 64 cpus and with cpu pinning enabled, a cpu 64 or greater is allocated for that pod where trafgen sender is executed. With bind-cpu option passed to trafgen cli, the cpu_stats struct was initialised wrongly.