[Feature Request]: Separate "Security" (Keys) from "config" on import/export functionality

[shoopes2]

Tell us your idea.

Current behavior: When a user exports their configuration from the Android Meshtastic app, the "config" option also includes a user's keys, so when that config is imported into another node, the keys are copied there as well.

Proposed behavior: The export/import configuration option should have another toggle switch for security keys. When a user imports a configuration, they would be able to not import security keys

Use case: A user has multiple nodes and wants them all to have similar configurations but doesn't want to manually configure each one nor for them to have identical public and private keys.

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct