feat(cli): support for reading and writing messages from/to files

[DM1-1]

PR Checklist

If you have any questions, you can refer to the Contributing Guide

What is the current behavior?

The current behavior of the CLI does not support reading and writing messages from/to files.

Issue Number

What is the new behavior?

The new behavior introduced by this PR allows the CLI to read messages from and write messages to files. This enhancement includes support for binary format for message representation.

Does this PR introduce a breaking change?

• Yes
• No (Assuming the new feature is backward compatible and does not break existing functionality)

Specific Instructions

• Ensure that the file reading and writing functions are thoroughly tested with various file sizes and binary formats.
• Verify that the new feature does not introduce any performance degradation in the CLI.
• Refactoring the previous code related to saving/loading configuration into a new utility file for handling file operations.

Other information

[DM1-1]

base64/hex

---

json/cbor

---

binary

---

loading for pub

---

--file-save

---

--file-write

[DM1-1]

save & load config

[ysfscream]

@DM1-1 GOOD JOB 👍

But I have a question: if we have successfully written it into the file, is it still necessary to print the information to the console? @Red-Asuka

[Red-Asuka]

@ysfscream I think --file-save does not need to print the specific message content, just output the path of the saved file. --file-write is generally used for continuous writing of readable text, it needs to output specific message content, but you can adjust the order, first output the message content, then prompt that the file was successfully written.