test: drop -master.peers, a flag this build no longer has (#9)

With diagnostics in place the crash is unambiguous: the container prints its
full usage text and exits 2, the Go flag package's response to an unknown flag.
Of everything the manifest passes, -dir, -s3, -filer, -volume.max and
-master.volumeSizeLimitMB all appear in that usage. -master.peers does not, and
neither does any other peer flag — the fork dropped it. Production does not pass
it either.

This is the same shape as the driver bug this repo exists to fix: config written
against upstream SeaweedFS, run against the Hanzo fork, failing on an identifier
the fork renamed or removed.

Co-authored-by: hanzo-dev <[email protected]>

.github/workflows/integration_test.yaml

@@ -127,7 +127,6 @@ jobs:
                       - -dir=/data
                       - -s3
                       - -filer
-                      - -master.peers=none
                       - -volume.max=10
                       - -master.volumeSizeLimitMB=16
                     ports: