Add state and description codes: Part 1

[0xB10C]

This PR adds the foundation and groundwork for the state and description codes. The handling by the Supervisor and the Middleware will come in part 2.

I leave this as a draft until BitBoxSwiss/bitbox02-api-go#17 is merged

[Stadicus]

Concept ACK, untested and no code review

[0xB10C]

fix typo correspointing -> corresponding

[Tomasvrba]

Light code review, I need caffeine XD

[0xB10C]

Thanks @Tomasvrba! Addressed.

[Tomasvrba]

ACK with two small comments:

1. When reviewing sequentially commit by commit, it's helpful when the commit message says why the commit does something, not what it does. For the first commit:

add: Redis sorted-set add, remove, gettop element
This adds the functionallity to add, remove or get top elements from a
Redis sorted set.

I can see from the code that it adds the functionallity to add, remove or get top elements from a Redis sorted set, but without looking at the rest of the commits in the PR first, it would be good to know why this is needed.

2. Another why, what's the logic behind the MapDescriptionCodePriority numbers?

[0xB10C]

Thank you Tom!

For context:
I originally planned to have one big PR with a detailed documentation and more context, but had to split it up into two due to interlinked Go Module dependencies for two projects in the same repo. Forgot to add the reasoning here. Will hopefully make more sense in the second PR.

I thought about answering your questions here, but I guess it makes more sense to link to the complete documentation in the second PR #305