Some updates in Lighthouse Book (#5000)

* Add jq in api-bn

* Update beaconstate size

* Add fields to web3signer API

* Link web3signer API

* Update /lighthouse/logs in table

* plural

* update slasher doc

* update FAQ

* Add link in validator section

* Add more info on state pruning

* Update database size

* Merge branch 'unstable' into book-update

* Revise Siren for vc to connect bn

* Merge branch 'book-update' of https://github.com/chong-he/lighthouse into book-update

* Corrections to siren faq

* Fix typos

* Update release date for 4.6.0

* Merge branch 'unstable' into book-update

book/src/slasher.md

@@ -17,7 +17,7 @@ of the immaturity of the slasher UX and the extra resources required.
 The slasher runs inside the same process as the beacon node, when enabled via the `--slasher` flag:
 
 ```
-lighthouse bn --slasher --debug-level debug
+lighthouse bn --slasher
 ```
 
 The slasher hooks into Lighthouse's block and attestation processing, and pushes messages into an
@@ -26,9 +26,6 @@ verifies the signatures of otherwise invalid messages. When a slasher batch upda
 messages are filtered for relevancy, and all relevant messages are checked for slashings and written
 to the slasher database.
 
-You **should** run with debug logs, so that you can see the slasher's internal machinations, and
-provide logs to the developers should you encounter any bugs.
-
 ## Configuration
 
 The slasher has several configuration options that control its functioning.