Improve usability of the hdc repository

[kiksotik]

Learn from other projects how organize the repository, the source-code, the packaging, the build-toolchain, etc...

HDC requires to conform to good practice of quite different software development cultures and its not sufficient to just follow a single set of conventions. Special care is needed to ensure the portability of the C code, which is currently too tailored to the specific conventions used by a single IDE (STM32CubeIDE)

Some sources for inspiration:

• https://github.com/min-protocol/min
• https://gitlab.com/mtausig/tiny-asn1
• https://github.com/afiskon/stm32-ssd1306
• https://github.com/lexus2k/tinyproto
  • Nice, tidy and very mature project. One can learn a lot from it!
  • ToDo: Does it make sense to replace the current HDC "packetizer" with TinyProto?
  • A good example to follow when porting HDC to Arduino.
  • https://github.com/nanoframework/nf-interpreter
  • Use https://cloudsmith.com/company/ for publication of binary artifacts.
  • Does it make sense to implement HDC for nanoFramework?