fix: setOutput value escaping and CI trigger path coverage

Use escapeMessage instead of escapeProperty for setOutput value — the
value is in the message body (after closing ]) where ] and ; are not
escaped. Also add trigger_filters.rs to ado-script workflow paths.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: jamesadevine

.github/workflows/ado-script.yml

@@ -5,6 +5,7 @@ on:
     paths:
       - "scripts/ado-script/**"
       - "src/compile/filter_ir.rs"
+      - "src/compile/extensions/trigger_filters.rs"
       - "Cargo.toml"
       - "Cargo.lock"
       - ".github/workflows/ado-script.yml"

scripts/ado-script/src/shared/__tests__/vso-logger.test.ts

@@ -23,10 +23,11 @@ describe("vso-logger", () => {
     ]);
   });
 
-  it("setOutput escapes ; in name and ] in value", () => {
+  it("setOutput escapes ; in name and passes ] through in value", () => {
     setOutput("a;b", "v]w");
     expect(writes[0]).toContain("variable=a%3Bb");
-    expect(writes[0]).toContain("]v%5Dw\n");
+    // Value is in the message body (after closing ]), so ] is NOT escaped
+    expect(writes[0]).toContain("]v]w\n");
   });
 
   it("addBuildTag emits a build tag command with message escaping", () => {

scripts/ado-script/src/shared/vso-logger.ts

@@ -31,7 +31,7 @@ function emit(line: string): void {
 
 export function setOutput(name: string, value: string): void {
   const safeName = escapeProperty(name);
-  const safeValue = escapeProperty(value);
+  const safeValue = escapeMessage(value);
   emit(`##vso[task.setvariable variable=${safeName};isOutput=true]${safeValue}`);
 }