Investigate espflash library usage

[MabezDev]

We don't have much from crates.io rev deps, but what we can, and should do is do a code search on Github/Gitlab to find library usage. From here, we can find what needs to be exposed in the library and what doesn't. It's also not that black and white, a module may be used because our other APIs are insufficient, or are tangled together forcing users to use both modules so keep that in mind.

[jessebraham]

A few projects which appears to be using espflash directly as a library:

• https://github.com/probe-rs/probe-rs/
• https://github.com/yanshay/esp-hal-app
• https://github.com/EyeTrackVR/FirmwareFlashingTool
• https://github.com/ivmarkov/espfactory
• https://github.com/3STechLabs-org/ESP32-Flasher
• https://github.com/QTShock/QTHub

This is not comprehensive, but investigating how these projects are using the library should at least give us a reasonable idea of how people are currently using espflash.

[nullstalgia]

I'm currently working on a binary crate (serial-terminal adjacent, still an early WIP) that intends to use espflash as a library! (I had just started to sniff through issues here to get a clearer picture on what I might need to look out for, and ran into this issue near the top. 😄)

But so far, something I've really appreciated is the ability to create helpers like Connections and Flashers, and then be able to consume them and get back the Port object for my terminal to use again without reconnecting! The ResetStrategy's request for a &mut Port also makes this easy, and is also appreciated.

If you have more questions about how I intend to use it as a library, or would like feedback as I get deeper into the project, I'd be happy to oblige!