chore(deployments): enable empty blocks creation on staging

[moul]

Addresses #863
Related with gnolang/hackerspace#9

Contributors Checklist

• Added new tests, or not needed, or not feasible
• Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory
• Updated the official documentation or not needed
• No breaking changes were made, or a BREAKING CHANGE: xxx message was included in the description
• Added references to related issues and PRs
• Provided any useful hints for running manual tests

Maintainers Checklist

• Checked that the author followed the guidelines in CONTRIBUTING.md
• Checked the conventional-commit (especially PR title and verb, presence of BREAKING CHANGE: in the body)
• Ensured that this PR is not a significant change or confirmed that the review/consideration process was appropriate for the change

[dongwon8247]

@moul When do you think this will be merged? in the current testnet3? or testnet4?

[r3v4s]

@moul seems to be creating empty block is false by default

gno/gno.land/cmd/gnoland/main.go

Lines 137 to 139 in 99633b9

	cfg := config.LoadOrMakeConfigWithOptions(rootDir, func(cfg *config.Config) {
	cfg.Consensus.CreateEmptyBlocks = false
	cfg.Consensus.CreateEmptyBlocksInterval = 60 * time.Second

But when running local node, it does create empty block every 60 seconds.
Shouldn't it be happen when above setting is set to true, not false?

or did I understood something wrong?

UPDATE

just saw this.
#863 (comment)

[moul]

@moul When do you think this will be merged? in the current testnet3? or testnet4?

This is a first try on staging (reset every hour). If everything goes smoothly, I think we can enable it on test3 and then keep it for the next versions.