bisync: fix equal_skipped test on S3 providers which recreate buckets

Some S3 providers, such as Wasabi and Alibaba, report success when
creating a bucket which already exists, so rclone logs that the bucket
was created. The during-sync hooks in the equal_skipped test create a
new Fs, which logged this in the middle of the bisync run and made the
log differ from the golden one. Ignore these messages.

cmd/bisync/bisync_test.go

@@ -109,6 +109,9 @@ var logReplacements = []string{
 	`^INFO  : .*cache expired.*$`, dropMe,
 	// ignore "Implicitly create directory" messages (TestnStorage:)
 	`^INFO  : .*Implicitly create directory.*$`, dropMe,
+	// ignore bucket creation messages from S3 providers which report success
+	// when creating a bucket which already exists (TestS3Wasabi:)
+	`^INFO  : .*: Bucket ".*" created with ACL ".*"$`, dropMe,
 	// ignore differences in backend features
 	`^.*?"HashType1":.*?$`, dropMe,
 	`^.*?"HashType2":.*?$`, dropMe,