There was a requirement that required arguments could not be positioned after an optional argument, but the deprecation of priority made the second argument to prioritisetransaction optional. So support that in RPCHelpMan.
Also format all named arguments in the same way (without the wrapping " even for strings), since the extended description already mentions the type and it feels odd to special case strings.
0-prioritisetransaction "txid" dummy fee_delta
1+prioritisetransaction "txid" ( dummy ) fee_delta
2 Accepts the transaction into mined blocks at a higher (or lower) priority
3
4 Arguments:
5-1. "txid" (string, required) The transaction id.
6-2. dummy (numeric, required) API-Compatibility for previous API. Must be zero or null.
7+1. txid (string, required) The transaction id.
8+2. dummy (numeric, optional, default=null) API-Compatibility for previous API. Must be zero or null.
9 DEPRECATED. For forward compatibility use named arguments and omit this parameter.
10 3. fee_delta (numeric, required) The fee value (in satoshis) to add (or subtract, if negative).
11 Note, that this value is not a fee rate. It is a value to modify absolute fee of the TX.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.