refactor(core): remove mistyped property value workaround

[AlessandroPomponio]

Summary

Removes a temporary workaround that silently coerced mistyped PropertyValue instances — where a string or list value was stored with NUMERIC_VALUE_TYPE — into the correct type. Instead, passing a mismatched value now raises a hard validation error, enforcing strict type correctness.

Closes #367

High-level Changes

• ado/schema/property_value.py: Removed the TEMP warning log paths and silent type-coercion logic that automatically upgraded NUMERIC_VALUE_TYPE values typed as str or list to STRING_VALUE_TYPE or VECTOR_VALUE_TYPE respectively. Validation now raises a ValueError with a descriptive message when the value type does not match the declared valueType.
• tests/schema/test_property_value.py: Replaced the pytest.xfail markers (which documented the previously tolerated misbehaviour) with pytest.raises(pydantic.ValidationError) assertions, confirming the cases now correctly fail.

Impact

Any PropertyValue instances that were previously persisted or created with a NUMERIC_VALUE_TYPE label but holding a str or list value can no longer be loaded or constructed. This is a breaking change for any data that relied on the old silent coercion; such records would need to be corrected at the source to carry the right valueType. All other value-type combinations are unaffected.

---

AI Disclosure: The code and this PR description were generated using IBM Bob and were reviewed manually.