feat(docker): statically allocate a network and IP addresses (backport #124)

[mergify]

This basically makes Petri in control of the IP address management instead of docker. This makes it easier to get static IP addresses even if the container is stopped. Before this, the Docker provider would provide DNS names instead of IP addresses, which is undesirable due to CometBFT/the SDK not having good support for DNS hostnames.

---

This is an automatic backport of pull request #124 done by Mergify.

[mergify]

Cherry-pick of 7ca1fb6 has failed:

On branch mergify/bp/release/v2.x.x/pr-124
Your branch is up to date with 'origin/release/v2.x.x'.

You are currently cherry-picking commit 7ca1fb6.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   core/go.mod
	both modified:   core/go.sum
	both modified:   core/provider/docker/docker_provider.go
	both modified:   core/provider/docker/network.go
	both modified:   core/provider/docker/task.go

no changes added to commit (use "git add" and/or "git commit -a")

Cherry-pick of 889bebb has failed:

On branch mergify/bp/release/v2.x.x/pr-124
Your branch is ahead of 'origin/release/v2.x.x' by 3 commits.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit 889bebb.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   core/provider/docker/docker_provider.go
	both modified:   core/provider/docker/network.go
	both modified:   core/provider/docker/task.go

no changes added to commit (use "git add" and/or "git commit -a")

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