getmempoolentry format differs from documentation #21468

<!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->

<!-- Describe the issue -->

There are divergences between the RPC reponse format and the documented response format.

<!--- What behavior did you expect? -->

Actual behavior

Here's the response I get from bitcoin-cli getmempoolentry <txid>:

{
  "fees": {
    "base": 0.00000144,
    "modified": 0.00000144,
    "ancestor": 0.00000144,
    "descendant": 0.00000144
  },
  "vsize": 144,
  "weight": 573,
  "fee": 0.00000144,
  "modifiedfee": 0.00000144,
  "time": 1616083370,
  "height": 1940743,
  "descendantcount": 1,
  "descendantsize": 144,
  "descendantfees": 144,
  "ancestorcount": 1,
  "ancestorsize": 144,
  "ancestorfees": 144,
  "wtxid": "18fcf877a1677bcdc828d338170f3d416cf866b0029147853fef29185f55db53",
  "depends": [
  ],
  "spentby": [
  ],
  "bip125-replaceable": false,
  "unbroadcast": false
}

According to the documentation (bitcoin-cli help getmempoolentry) I have encountered two divergences:

• size field described in the docs should be renamed to vsize
• docs should add the unbroadcasted field

<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->

Run bitcoin-cli help getmempoolentry and compare against the documentation hosted on bitcoin.org

<!--- How reliably can you reproduce the issue, what are the steps to do so? -->

System information Tested on head (v21.99.0-b972913c330a)

<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

<!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->

<!-- Any extra information that might be useful in the debugging process. -->

<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->

You can fix that by clicking on " Edit Page " on the page you linked to. This repository is only about Bitcoin Core bugs, not bitcoin.org related bugs.