Make option syntax clear and consistent

[alexandratran]

There are some inconsistencies with how we present the syntax of various CLI options in the reference. For example:

--rpc-http-tls-cipher-suite=<cipherSuiteName>[, <cipherSuiteName>...]

--bootnodes[=<enode://id@host:port>[,<enode://id@host:port>...]...]

--net-restrict=<subnet>[,<subnet>,...]

--banned-node-ids=<bannedNodeId>[,<bannedNodeId>...]...

These are some inconsistent examples of how we denote comma-separated lists, and there are still other variants. Also, we currently use square brackets to denote an optional value, but some options might require using square brackets for arrays, which could cause confusion. We should decide on a consistent and clear way to document these types of options.

[m4sterbunny]

Recommendations for style to apply:

Do: Use <name>=<true|false> for boolean options with default specified:
--auto-log-bloom-caching-enabled=<true|false> default is false
NOT --auto-log-bloom-caching-enabled[=<true|false>] default is false

Do: Use <name>=<item>[,<item>...] for a required item, with optional comma-separated additional items:
--bootnodes=<source>[,<source>...]
NOT --bootnodes[=<enode://id@host:port>[,<enode://id@host:port>...]...]

Do: Use --flag=[<item1>,<item2>,...] for optional arrays

WDYT?

[alexandratran]

@m4sterbunny That sounds good to me.

[m4sterbunny]

Tag along fix: replace "It may take up to multiple days"
with "It may take several days"

[m4sterbunny]

Note on the proposed t/f solution: no go!
there are instances where the [= is correct.
For example "--bonsai-limit-trie-logs-enabled"
LLM looking at the besu code tells me: fallbackValue = "true" means it can be used as a flag (without a value) and when used as a flag, it defaults to true
(If arity = "1" were set, it would require a value)
Tests also show it used as a flag:
So given that --bonsai-limit-trie-logs-enabled can be used as a flag; that means docs should give [=<true|false>]