Support for useFakeTimers('modern')

I would like to be able to use this lib to mock out dynamo but am reaching a blocking issue when using jest v26 features, namely useFakeTimers('modern').

Using the preset, any test that calls into the local db results in the following error:

TypeError: Cannot read property 'useFakeTimers' of undefined
...
jest.useFakeTimers(`modern`);
     ^

I attempted to patch in the calls to useFakeTimers to accept the "modern" type argument, but that did not change the outcome. Any test that does not include the call to the db works as expected. I am fairly new to using jest so I’m not counting out user error, but it seems like something is off only when this lib is involved in the test. Worth noting, this will become the default in the next major version of jest.

[mgmolisani]

Sure. Here is basically the testing I was able to do to see where tests failed to run. It did not matter where I set jest timers to 'modern'. timers: 'modern' in config, beforeAll, beforeEach, in the test body, all failed similarly.

describe(`test`, () => {
  it(`uses dynalite and modern timers`, async () => {
    jest.useFakeTimers(`modern`)
    // ^ This fails with that extremely weird error suggesting jest is undefined
    await someFunctionThatUsesTheDb()
  })
  it(`uses dynalite and legacy timers`, async () => {
    jest.useFakeTimers()
    // ^ This works but doesn't provide new APIs and will not be the default in jest v27
    await someFunctionThatUsesTheDb()
  })
  it(`doesnt use dynalite `, async () => {
    jest.useFakeTimers(`modern`)
    // ^ This works fine
    await someFunctionThatDoesntUseTheDb()
  })
})

[freshollie]

Release as v3.2.2