2.2.X Proposed Protobuf changes

On the device, we will incremement the DEVICESTATE_VERSION, so folks will need to re-provision their devices. This also gives you all on the app / client front a clean slate. Most of this is removing, not re-indexing deprecated protobufs. We'll save re-indexing for 3.0, since that will be a breaking change for the protocol. Clients need to source some of the removed fields from MyNodeInfo on DeviceMetadata now

This shouldn't be a breaking change, per-se except for the device which as I mentioned will incremement the DEVICESTATE_VERSION and reprovision. Some clients may respond differently to the removal of protobuf fields, so I'm not entirely sure how that looks in each one. In any account, apps / clients will need to do the minimum version prompt when attempting to pair 2.0/2.1x devices to ensure that things move forward. I think it should be a pretty smooth transition.

If it doesn't work out on the field removal front in MyNodeInfo, we can go back on that. My preference was to remove those before 3.0, to slowly transition to phasing those fields out rather than completely gutting like we did from 1.2 to 2.0, which placed a large burden on all of the clients.

meshtastic / protobufs

2.2.X Proposed Protobuf changes #368