Include ref.parent matches in events by-reference navigation

[Copilot]

/events/by-ref/{referenceId} only matched reference:{id}, so clicking a Parent link failed when child events stored the relationship in ref.parent and no standalone parent event existed. This updates by-ref lookup semantics to return related events for that parent reference value in both global and project-scoped routes.

• API query behavior

  • Updated both by-ref endpoints in EventController to search:
    • direct event reference (reference:{id})
    • parent linkage (ref.parent:{id})
  • This makes Parent navigation resolve for scope-based/client-generated parent references.

• Regression coverage

  • Updated integration tests in EventControllerTests to assert by-ref results now include:
    • parent + children when both exist
    • children when only ref.parent links exist
    • equivalent behavior for project-scoped by-ref route

return await GetInternalAsync(
    sf,
    ti,
    $"(reference:{referenceId} OR ref.parent:{referenceId})",
    null,
    mode,
    page,
    limit,
    before,
    after
);

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}