Pattern file names and filename field should be in single quotes, not double

[taylorlm88]

Before we talked about file paths needing to be in single quotes, not double quotes, in a yaml file. Pattern files may just be filenames, in which case this is not an issue, but the user can also provide an absolute path to a pattern in the pattern field in order to override the pattern library, if they happen to have patterns outside the library they want to use. If the user does provide a full path instead of just the pattern's filename, double quotes will cause the same issue it causes with the rig and pattern library paths. So to be safe, the pattern names should also be exported as characters with single quotes, instead of strings with double quotes.

[taylorlm88]

Just realized the filename parameter for the startRecording command from the camera can also be an absolute path and therefore should be in single quotes as well.

[mbreiser]

Fixed in commit c4f2279 (v0.8.1).

Root cause: appendCommand() used yamlStr() (double quotes) for both the controller pattern field and all string-typed plugin params. Double-quoted YAML strings interpret backslash escape sequences, so Windows paths like C:\patterns\test.pat would be mangled.

Fix: Switched to yamlPath() (single quotes) for:

1. The controller pattern field (line 286)
2. All string-typed plugin params in the params loop

Single-quoted YAML strings treat backslashes as literal characters. The roundtrip parser already handles both quote styles.