bisync: account for differences in backend features on integration tests - see #5679

Before this change, integration tests often could not be run on backends with
differing features from the local system that goldenized them. In particular,
differences in modtime precision, checksum support, and encoding would cause
false positives. After this change, the tests more accurately account for the
features of the backend being tested, which allows us to see true positives
more clearly, and more meaningfully assess whether a backend is supported.

cmd/bisync/log.go

@@ -7,6 +7,7 @@ import (
 	"strings"
 
 	"github.com/rclone/rclone/fs"
+	"github.com/rclone/rclone/lib/encoder"
 	"github.com/rclone/rclone/lib/terminal"
 )
 
@@ -36,6 +37,7 @@ func (b *bisyncRun) indent(tag, file, msg string) {
 // escapePath will escape control characters in path.
 // It won't quote just due to backslashes on Windows.
 func escapePath(path string, forceQuotes bool) string {
+	path = encode(path)
 	test := path
 	if runtime.GOOS == "windows" {
 		test = strings.ReplaceAll(path, "\\", "/")
@@ -58,3 +60,7 @@ func Color(style string, s string) string {
 	terminal.Start()
 	return style + s + terminal.Reset
 }
+
+func encode(s string) string {
+	return encoder.OS.ToStandardPath(encoder.OS.FromStandardPath(s))
+}