Updated the moqui.server.Visit relationship type from one to one-nofk to remove the foreign key constraint on the Visit entity.

[dixitdeepak]

Motivation

The one relationship type generates a database-level foreign key (FK) constraint, which causes issues during visit data purging. When visit/visitor records are purged, the FK constraint prevents deletion of related records, leading to constraint violations.

This aligns with the existing pattern used in ArtifactHit, which already uses one-nofk for its Visit relationship — reinforcing that FK constraints are not appropriate for transient session/visit data.

• Visit and visitor data is transient/purgeable by nature — maintaining a hard FK reference defeats the purpose of data purging
• Consistent with how ArtifactHit handles the same relationship
• No functional impact on query behavior; the logical relationship is preserved without the DB constraint
• Enables clean purging of visit/visitor data without constraint violations