message: Stop always storing blocks from whitelisted peers
  There is no reason to wish to store blocks on disk always just
  because a peer is whitelisted. This appears to be a historical
  quirk to avoid breaking things when the accept limits were added.
  Github-Pull:
  Rebased-From:
diff: @@ -2509,11 +2509,7 @@ bool static ProcessMessage(CNode* pfrom, const std::string& strCommand, CDataStr
  LogPrint(BCLog::NET, "received block %s peer=%d\n", pblock->GetHash().ToString(), pfrom->GetId());
  - // Process all blocks from whitelisted peers, even if not requested,
  - // unless we're still syncing with the network.
  - // Such an unrequested block may still be processed, subject to the
  - // conditions in AcceptBlock().
  - bool forceProcessing = pfrom->fWhitelisted && !IsInitialBlockDownload();
  + bool forceProcessing = false;
  const uint256 hash(pblock->GetHash());
  {
  LOCK(cs_main);
  