Fix recurring TSA onboarding failure in release builds (#41167)
The 1ES Official governed template (v2/Microsoft.Official.yml) force-runs the TSA onboard/upload step even though globalSdl.tsa.enabled was false. With no tsaoptions.json, TSA auto-derives the codebase name 'microsoft_Microsoft.WSL_microsoft/WSL', which contains the illegal characters '.' and '/'. Onboarding therefore fails with PreconditionFailed and 'Guardian exited with an error exit code: 1' on every release build. Add .config/tsaoptions.json with an explicit, sanitized codebase name and wire the release pipeline's globalSdl.tsa to consume it via configFile. Bugs are routed to the WSL area path in the OS project. Co-authored-by: Ben Hillis <benhill@ntdev.microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: aa582972-8aa3-43c9-9fe3-6a9ff2bc1ab2