Test: v0 pr_validation behavior with $ref into code/common/

[hdamker]

What type of PR is this?

tests

What this PR does / why we need it:

Test PR to verify how the legacy v0 pr_validation workflow behaves on API specs that use $ref into code/common/.

ReleaseTest's three sample API specs already use this pattern; this PR adds a no-op marker line to sample-service.yaml to trigger the workflow.

The test feeds a pre-rollout decision: when API repositories migrate to commonalities_release: r4.2 and switch their specs to $ref into bundled common schemas, must the legacy pr_validation_caller.yml be removed in lockstep, or can it coexist?

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Diagnostic PR. Outcomes:

• v0 errors → v0 must be removed in lockstep with r4.2 migration
• v0 succeeds → no rollout-sequencing constraint
• v0 noise → judgment call on codeowner UX

Will be closed without merging once the v0 behavior is observed.

Changelog input

 release-note

Additional documentation

docs

[camara-validation]

CAMARA Validation — FAIL

4 errors, 18 warnings, 15 hints | Profile: standard

View full results

[github-actions]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	4		0	0.01s
❌ API	spectral	3		2	4.23s
✅ GHERKIN	gherkin-lint	1		0	0.35s
✅ REPOSITORY	git_diff	yes		no	0.0s
✅ REPOSITORY	secretlint	yes		no	0.65s
✅ YAML	yamllint	3		0	0.46s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by