Rebrand Library OR Extract non-Arduino logging core into another library

[phillipjohnston]

I had this thought yesterday, because the core logic I used is general C++ and not tied to Arduino. I've created a repo for a C++ embedded logger to house some of the core code and generalize it. The goal is that the core library would live there, and the arduino-logging library would submodule it, provide arduino-specific logging strategies, examples, and support the library organizational structure.

There's a two problems I'm thinking about ways to address:

I like a more organized project structure, and Arduino enforces a top-level file set for libraries, or else things aren't properly discovered I think I can solve this with wrapper headers, but I ran into some include problems earlier today, so I need to work out the kinks There are C++14/C++17 features that I use in the original library that had to be stripped out for the Arduino ecosystem, I'm not sure how I want to manage that dichotomy