Forging fails when genesis block timestamp is in the future

[ManuGowda]

Expected behavior

When we migrate Lisk Core from 2.x.x to 3.x.x, the blockchain should be able to start considering genesis block timestamp in future.

More details can be found in LIP: https://github.com/LiskHQ/lips/blob/master/proposals/lip-0035.md#general-block-properties

Actual behavior

When the genesis block timestamp is in the future(10sec, 1hr, 2hr, 1day, etc..), the application fails to forge blocks.

12:14:01 INFO lisk-framework: Node ready and launched (module=lisk:app)
12:14:02 ERROR lisk-framework: Cannot read property 'address' of undefined (module=lisk:app)
Message: Cannot read property 'address' of undefined
 Trace: TypeError: Cannot read property 'address' of undefined
    at Forger.forge (lisk-sdk/framework/src/node/forger/forger.ts:387:57)
    at Node._forgingTask (lisk-sdk/framework/src/node/node.ts:680:4)
    at Timeout._onTimeout (lisk-sdk/elements/lisk-utils/src/job_handlers/scheduler.ts:47:5)

Steps to reproduce

• Create timestamp with(2hrs) in the future
• Update devnet genesis block timestamp field with the generated value
• Start the application and observe the error

Which version(s) does this affect? (Environment, OS, etc...)

5.x.x, development