Improve report utilities

[Keith-CY]

Now neuron supports exporting debug information to analyze issues users have submitted, and most cases can be fixed because they have certain patterns, which will be facilitated by self-service debug information analysis

But the following actions are not included:

1. cannot export the entire log of ckb node/light client because the size is huge;
2. cannot export transactions that are not signed/submitted successfully because
   1. a transaction is too complex to be printed in log file;
   2. it's hard to determine if a transaction should be reported, e.g., a rejected transaction that is pending for a long time;
3. cannot export blocked block/transaction because a block/transaction is too complex to be printed in log file.

For point 1, a shortcut to the directory of ckb node log can be added so users can open the folder easily when the entire log is required.

For point 2 and 3, a runtime log may be introduced so necessary information can be exported selectively.

The runtime log may keep printing real-time logs, e.g.

1. synced transaction, a functional button could be provided to inspect the modification along with this transaction, for instance, balance update, live cells update
2. submitted transaction with a functional button to inspect the modification of neuron's status
3. rejected/failed to sign transaction with a functional button to dump it for analysis
4. synced block, similar to synced transaction
5. error, with a functional button to export its context, e.g. error tracing, wallet status(live cells, block height)

Besides, I would suggest adding interactive utilities with the runtime log to make it extensible. E.g.

1. basic query to fetch information of an address(script info, live cells, deal cells, etc), submit a raw transaction to sign.,
2. basic query to fetch transactions of various statuses (committed, pending, rejected)
3. command line tool to run lumos method
4. filters to filter log entries by specific condition
   1. log level
   2. keyword
   3. type
   4. range
   5. freeze/lock to disable printing more logs(I found a term of it, "Now Mode")
5. real-time statistic, shows the difference in status introduced by those logs, e.g cell count, address count, block count, transaction count, during this launch

Some examples:

@yanguoyu @homura @devchenyan @WhiteMinds @zhangyouxin do you have more ideas to improve debug/report?

[Keith-CY]

Why is this issue marked Hold on @Danie0918

[Danie0918]

Why is this issue marked Hold on @Danie0918

This one is based on prioritization and has no plans to start yet.

I'll start on the next version.