Feat/support referencing translations that sit in a release

[SamHemingway]

Description

As it stands, if we have a translation metadata document that refers to a translated document that sits in a release, we get a validation error.

The validation logic currently checks the published or draft perspectives.

This PR lets the validation use the raw perspective, so it can validate against versioned documents too.

What to review

Is this going to break anything unexpected? It should purely be additive.

Also, the experience on the translations metadata document is confusing when looking at the published perspective:

But makes sense when you're looking at the perspective in which the translation exists:

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​typescript-eslint/​parser@​7.6.0 ⏵ 7.18.0
	eslint-config-prettier@​9.1.0 ⏵ 9.1.2
	@​commitlint/​cli@​19.2.1 ⏵ 19.8.1	+1		+1
	@​sanity/​semantic-release-preset@​4.1.7 ⏵ 4.1.8				+1
	@​sanity/​mutator@​3.67.1 ⏵ 3.99.0			-1
	prettier-plugin-packagejson@​2.4.14 ⏵ 2.5.19	+1		+1
	eslint-plugin-simple-import-sort@​12.0.0 ⏵ 12.1.1	+1		+1
	@​types/​react@​18.3.17 ⏵ 18.3.26	+1		+2	+1
	@​typescript-eslint/​eslint-plugin@​7.6.0 ⏵ 7.18.0	+1		+1
	eslint-plugin-react@​7.34.1 ⏵ 7.37.5	+1
	sanity-plugin-utils@​1.6.7 ⏵ 1.7.0	+1			+5
	eslint-config-sanity@​7.1.2 ⏵ 7.1.4
	@​sanity/​ui@​3.0.5 ⏵ 3.1.10	+1		+2
	@​sanity/​plugin-kit@​3.1.10 ⏵ 3.1.12	+3			+1
	styled-components@​6.1.13 ⏵ 6.1.19	+1		+1
	@​commitlint/​config-conventional@​19.1.0 ⏵ 19.8.1
	eslint-plugin-prettier@​5.1.3 ⏵ 5.5.4	+1
	prettier@​3.4.2 ⏵ 3.6.2	+1
	eslint-plugin-react-hooks@​4.6.0 ⏵ 4.6.2	+1
	eslint@​8.57.0 ⏵ 8.57.1
	lint-staged@​15.2.11 ⏵ 15.5.2			+1	+1
	sanity@​3.67.1 ⏵ 3.99.0
	semantic-release@​23.0.7 ⏵ 23.1.1	+1			+5

View full report