Make protocol utils more convenient

[ThiefMaster]

• find_keys: Print the machine ID at the beginning and try all the known keys of existing machines first since it seems quite common that keys are reused
• dump_memory: Take the target filename and optional memory range as CLI args

Both are things I manually edited into the code in a very messy way (for the keys I just edited the start value for each key to the one I thought it might be), but they sound like the kind of things that could save everyone a bit of time when adding new machines.

Reusing existing keys would likely require a bit of refactoring since right now they aren't particularly accessible from "outside", but the other suggestion should be quite easy. Happy to send a PR if you are fine with it (and don't mind having clap as a dependency for this script)

[medusalix]

Thanks for the suggestions, I'll be happy to accept a PR to improve these tools.

I think the first thing to do would be to turn the examples into applications (moving them to src/bin/). Then we could also add clap as a dependency for the binaries.

Regarding the known keys, I'd be totally fine with adding an array of keys from existing devices. I don't think refactoring the devices to expose the keys would be worth it, in my opinion.

For the dump_memory and dump_eeprom, I would even suggest making the memory range arguments mandatory. Right now these scripts are kind of designed for the older Miele appliances with MELPS 740 microcontrollers, but for newer devices with a memory space larger than 0xffff you almost always have to know the region you're dumping before running the script.

[medusalix]

Another issue worth mentioning is that the dump_eeprom script currently misbehaves on newer appliances. Older devices used to accept a word address when reading from or writing to the EEPROM. At some point, Miele decided to specify the address in bytes instead. So it would be great if that script accepted a flag to switch between these two cases.