fix: fix timestamp inconsistencies between Windows and Linux

[TedRio]

No description provided.

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 98.13%. Comparing base (a42daaf) to head (e660546).

Files	Patch %	Lines
...c/pykiso/lib/connectors/cc_pcan_can/cc_pcan_can.py	66.66%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #459      +/-   ##
==========================================
- Coverage   98.17%   98.13%   -0.05%     
==========================================
  Files          84       84              
  Lines        6699     6707       +8     
==========================================
+ Hits         6577     6582       +5     
- Misses        122      125       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sebastianpfischer]

Suggested change

	try:
	# use to avoid timestamp inconsistances between pykiso and python can
	import uptime
	if uptime.boottime() is None:
	boottime_epoch = 0
	else:
	boottime_epoch = uptime.boottime().timestamp()
	except ImportError:
	boottime_epoch = 0
	boottime_epoch = 0
	try:
	# use to avoid timestamp inconsistances between pykiso and python can in linux
	import uptime
	if not uptime.boottime():
	boottime_epoch = uptime.boottime().timestamp()
	except:
	pass

[sebclrsn]

I personally find it more explicit to set it to 0 in all failing cases

[Pog3k]

I also like the fact that we don't catch all errors