Inline blocks should honor the "unique value per language" (shared property) setting

Properties on inline blocks are always stored per language version, regardless of how the property is configured on the content type. A property marked as not unique per language — i.e. intended to be shared across all languages — behaves as language-specific when the block is inline, so editors get divergent values in each language with no warning.

Reproduction:
1. Create a content type with two properties: one marked as unique value per language, and one marked as not unique per language (shared).
2. Create a page with two language versions.
3. Add a block of that content type inline inside a content area on the page.
4. In the first language version, set values for both properties.
5. Switch to the second language version and change the shared property's value.
6. Return to the first language version and inspect that property.

The shared property holds a different value in each language version, while the same content type used as a shared block from the block tree respects the setting correctly — the divergence only occurs when the block is inline

Expected:
Inline block properties should respect the language-uniqueness configured on the content type. A shared property should resolve to one value across every language version of the owning page.

Why it matters:
Shared properties are how editors keep non-translatable data consistent — identifiers, product codes, tracking keys, brand labels, configuration toggles. On multilingual sites, inline blocks silently break that guarantee: values drift as each language is edited, and there's nothing in the UI signaling that the setting doesn't apply here. Teams either avoid inline blocks entirely on multilingual sites — losing their main advantage of not cluttering the block tree — or manually reconcile values across every language.