Allow override of DB id

[mkysel]

During development it seems to be pretty common to change the nodeId from one to another. We have to nuke the DB to fix this.

Can we simply change the NodeId in the DB without catastrophic consequences?

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “Queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “Hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[neekolas]

In the case where the node ID changes, we want to do more than just skip the check. We want all messages in the database to be wiped. Otherwise we can get into a weird situation where you have messages originated from a node ID that doesn't exist, and other peers who are syncing from this node will have inconsistent records. That will make debugging sync issues much harder.