feat: override timeout commit via --timeout-commit (backport #4103)

[mergify]

Closes #4080

Testing

1. ./scripts/single-node.sh now makes blocks faster 🎊
2. ./scripts/arabica.sh throws an error if you try to add --timeout-commit 1s

Error: the --timeout-commit flag was used on arabica-11 but it is unsupported on public networks: arabica-11, mocha-4, celestia. The --timeout-commit flag should only be used on private testnets.

[mergify]

Cherry-pick of d20916c has failed:

On branch mergify/bp/v3.x/pr-4103
Your branch is up to date with 'origin/v3.x'.

You are currently cherry-picking commit d20916c7.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   Makefile
	modified:   README.md
	modified:   app/app.go
	modified:   app/app_test.go
	modified:   app/test/upgrade_test.go
	modified:   cmd/celestia-appd/cmd/app_exporter.go
	modified:   cmd/celestia-appd/cmd/app_server.go
	modified:   cmd/celestia-appd/cmd/root.go
	modified:   pkg/appconsts/chain_ids.go
	modified:   test/tokenfilter/setup.go
	modified:   test/util/malicious/app.go
	modified:   test/util/test_app.go
	modified:   test/util/testnode/config.go
	modified:   tools/chainbuilder/integration_test.go
	modified:   tools/chainbuilder/main.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   cmd/celestia-appd/cmd/start.go
	both modified:   scripts/single-node.sh

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[rootulp]

This is technically Go API breaking b/c app.New() has an additional parameter.

[cmwaters]

This is technically Go API breaking b/c app.New() has an additional parameter.

You could probably do this in a non-breaking way by utilising baseapp options, but I think we can allow this to slide - I can't imagine there are too many users of the app.New() but good to avoid this if we can in the future