benchmark: Fix crash in net benchmarks

[matthewloring]

Checklist

• tests and code linting passes
  • test-tick-processor/test-domain-no-error-handler-abort-on-uncaught
    are failing but these should be unrelated.
• a test and/or benchmark is included
• the commit message follows commit guidelines

Affected core subsystem(s)

benchmark

Description of change

Net benchmarks create partial event emitters that do not have all of the
required event emitter functions. They currently mock out on, once,
and emit functions. This change mocks out prependListener as well to
avoid crashing in _stream_readable.

Fixes #6405

[addaleax]

LGTM

test-tick-processor/test-domain-no-error-handler-abort-on-uncaught are failing but these should be unrelated.

it is.

[mscdex]

lint: https://ci.nodejs.org/job/node-test-linter/2194/

[jasnell]

LGTM

[JungMinu]

LGTM

[matthewloring]

Could we address #6405 (comment) in a follow PR or should we set up a way to optionally run benchmarks for correctness in the CI here?

[matthewloring]

Landed in 89164a0

[MylesBorins]

@matthewloring should this be backported?

[matthewloring]

Probably not a big deal since these benchmarks will be run from source and not from a distribution.