Reject duplicate entity property names

[elpete]

Closes #59

Issue review

Recommendation: 9/10 — preserve and test. An explicit column mapping must always win over an identically named physical column; otherwise an entity silently hydrates incorrect data.

Reproduction and follow-up

The original reported behavior cannot be reproduced on current next with qb@14.0.0-beta.3: an explicit username to first_name mapping wins even though the table also has a physical username column.

Lucee does accept two entity properties with the same name and collapses them in component metadata. Quick now detects duplicate local property declarations during its cached metadata inspection and throws QuickDuplicateProperty, avoiding an ambiguous generated accessor and column mapping.

Implementation

• keeps the explicit-column collision fixture and public getter regression
• adds a public entity-resolution regression for duplicate property names
• validates only declarations in the local component source, leaving inherited properties alone
• supports script and tag property declarations when source is available

Validation

• focused Lucee 6 AttributeSpec: 19 passed, 0 failed, 0 errors
• formatting check passed
• git diff --check passed

Uses qb@14.0.0-beta.3 and targets next.