Abstraction needed for user-editable configuration

[brainwavecoder9]

trafficstars

Creating an issue for this because it has been a persistent need that merits a bigger discussion. Would like to see a solution that lets users maintain local configuration regardless of what happens with the project.

User-related configuration data is currently buried within code, meaning that configuration changes require code changes and need to be merged/managed. The approach has also changed a few times.

It has been suggested that 777 will address this (I don't think it will). I previously made an attempt at solving this before I knew about the move to Draccus was happening (also did not address this), and Discord user @nick_builds (whose github handle is TBD) also recently made an attempt to address this. We are planning a discussion around this and would invite others to participate.

This would ideally be a complete separation of user-managed configuration details (E.g., USB ports for arms, camera names) so that project owners could make implementation changes at-will without users having to merge or manage user-configuration data.

E.g., pulling the latest code or switching branches shouldn't change which USB port my robot is using.