test: http2 add timeout no callback test case

[trivikr]

This code change adds a test case where server.setTimeout is called without a callback
Refs: #14985

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• commit message follows commit guidelines

Affected core subsystem(s)

test, http2

[watilde]

ci: https://ci.nodejs.org/job/node-test-pull-request/10583/

[refack]

@trivikr thanks for contribution.

CI complains that there's a typo in test-http2-server-settimeout-no-callback.js:21:12:

not ok 926 parallel/test-http2-server-settimeout-no-callback
  ---
  duration_ms: 0.118
  severity: fail
  stack: |-
    assert.js:45
      throw new errors.AssertionError({
      ^
    
    AssertionError [ERR_ASSERTION]: 'Callback must be a function' === 'callback must be a function'
        at Object.<anonymous> (/data/iojs/build/workspace/node-test-commit-linuxone/nodes/rhel72-s390x/test/common/index.js:723:16)
        at Object.<anonymous> (/data/iojs/build/workspace/node-test-commit-linuxone/nodes/rhel72-s390x/test/common/index.js:517:15)
        at expectedException (assert.js:651:19)
        at innerThrows (assert.js:685:21)
        at Function.throws (assert.js:702:3)
        at Object.expectsError (/data/iojs/build/workspace/node-test-commit-linuxone/nodes/rhel72-s390x/test/common/index.js:745:12)
        at notFunctions.forEach (/data/iojs/build/workspace/node-test-commit-linuxone/nodes/rhel72-s390x/test/parallel/test-http2-server-settimeout-no-callback.js:21:12)
        at Array.forEach (<anonymous>)
        at verifyCallbacks (/data/iojs/build/workspace/node-test-commit-linuxone/nodes/rhel72-s390x/test/parallel/test-http2-server-settimeout-no-callback.js:20:16)
        at Object.<anonymous> (/data/iojs/build/workspace/node-test-commit-linuxone/nodes/rhel72-s390x/test/parallel/test-http2-server-settimeout-no-callback.js:35:3)
  ...

[refack]

Capital C in Callback.

[refack]

P.S. @trivikr now that you're a "seasoned" contributor, you might want to pick up a few common practices:

1. You can quickly run a changed test with node test/parallel/test-http2-server-settimeout-no-callback.js and get immediate feedback. (just make sure your node binary is recent enough, either build localy or get the latest nightly from https://nodejs.org/download/nightly/)
2. Run the linter locally (make lint-js)
3. For changes in the core code, you should build and run the test suite locally

This and more information in https://github.com/nodejs/node/blob/master/CONTRIBUTING.md

Hope to see you contribute even more in the future 😉

[refack]

Quick CI: https://ci.nodejs.org/job/node-test-commit-linuxone/9231/ ✔️

[trivikr]

Thanks @refack
I've been using the following command to run tests
python tools/test.py -J --mode=release parallel/test-http2-server-settimeout-no-callback
In this case I would have forgotten to run tests after adding message in invalidCallBackError, my bad.

The python command is more visual, it shows success and failure using + and -

[mcollina]

CI: https://ci.nodejs.org/job/node-test-pull-request/10756/

[mcollina]

Landing.

[mcollina]

LGTM

[mcollina]

Landed as e2015b5.