Do not hardcode package cstates

Different platforms may support different package cstate.
Instead of hardcoded package cstates to check in turbostat, we should
a. blindly check all possible package cstates, and leverage turbostat to give meaningful output (turbostat has per-platform profile which should expose available package cstates only)
b. check CPUID.5, it exposes sub-cstates for supported cstates only, and we can leverage that info.

Start by locating the turbostat package-cstate checks in the shell code and review how turbostat exposes per-platform profiles. Compare that path with the CPUID.5 information described in the issue. Done means supported package cstates are detected per platform without hardcoded checks and turbostat output remains meaningful.

Written by the indexing model from the issue text.