Incorrect alarm interpretation about bms_connector

[sofkaski]

From the debug output:

1. The second response that contains alarms is: ~20004600806200001000020002000000020000000000000000060000000000000000140002000000020182001000000000000000000010EB21
2. The part that contains Alarm event 1 - Alarm event 6 is 000200000002. From SEPLOS BMS Communication Protocol_V2.0 .pdf we can interpret this so that Alarm event 2 and Alarm event 6 have non-zero values.

[sofkaski]

I can try to fix this and make a PR for review.

[sofkaski]

I have a fix proposal in https://github.com/sofkaski/bms_connector/tree/fix-alarm-mapping. It contains also unrelated commits that resolve Ruff findings. I was about to make a PR against next-branch as instructed in contributing guidelines, but noticed that the the next-branch is far behind the main. @flip555 could you rebase/merge next-branch to the level of main?

(If I make the PR now, it would look a bit crowded, since it would also include commits from main).

[sofkaski]

I have the version from my branch running in my environment (Seplos V2): Based on first few update rounds it seems to be working, but I would assume to get more alarms tomorrow to see if they are correct.