as the context information might not be available on all
devices, e.g. in our GitHub CI VM the CPU frequency.

Wrap setting of dict entry in a try, except blog that throws warn-
ings when a value cannot be obtained.

We decided on a more tailored approach and will only wrap the
effected parts of the CPU info, not all of them.

as the function is not available on all devices, e.g. apple ARM in
our GitHub CI. In that case, set frequency avg, min, max to zero.

as we set the CPU frequency to zero when it is not available on the
host machine. That is the case in the GitHub CI. We don't want this
test to fail when there is the frequency 0 as then the CPUInfo has
been correctly populated.

as this is what is thrown by PSUTIL if the information is not
available in the current machine.