Fix genesis block creation logic

[nagdahimanshu]

Expected behavior

Genesis block should be created based on lisk-core instance

Actual behavior

Currently, genesis block is created based on default application instance. This results in the error when starting node with migrated genesis block:

2023-08-29T08:05:34.629Z INFO Himanshus-MBP.fritz.box application 85680 Registered legacy module has command registerKeys
2023-08-29T08:05:34.646Z INFO Himanshus-MBP.fritz.box application 85680 [stateRoot=c87b4dca0c82e31455f28984322c189b33c19216ccae19be5f6a5c90a7201682 height=20171933] Start caching genesis state
    Error: Invalid state root `Not matching with expected`
2023-08-29T08:05:37.445Z INFO Himanshus-MBP.fritz.box application 85680 [errorCode=2 message=process.exit] Application shutdown started

Steps to reproduce

• Create genesis block using migrator (testnet or mainnet)
• Start node with the migrated genesis block
• Ref genesis-block:create is missing optional flags lisk-sdk#8909

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

v2.0.0-beta.2