[TypeSpecValidation] Compile should fail if generated swaggers are outside org folder

Some existing specs have invalid values for setting "emitter-output-dir", like "{output-dir}". This causes "tsp compile" to generate swaggers in the repo root, **outside** the organization folder. Which further confuses rules like Compile, into not detecting that the actual spec swaggers aren't being updated.

Example: https://github.com/Azure/azure-rest-api-specs-pr/actions/runs/16562512692/job/46834910004#step:4:200

To prevent this, if any generated swaggers are outside the org folder (e.g. `specification/widget`), fail immediately. Specs should **never** write outside their org folder. Any failures should be fixed, not suppressed.

Even further, if we detect the spec is folder structure v2, we can enforce that all swaggers are written under the **current** folder, not just the org folder.

Related:
- #38543

Spec Fixes:
- https://github.com/Azure/azure-rest-api-specs-pr/pull/25271