OXEAN-133 Add nested relation filter opt-in

[GiuseppeXD]

Description ✍️

Make nested relation filters opt-in. Graphoid no longer generates relation filter arguments unless the association declares graphoid_nested_filter: true.

Generated to-many relation fields continue to exclude where, preventing selected relation filters from entering Graphoid's processor.

Overview 🔍

class Sheet < ApplicationRecord
  belongs_to :project, graphoid_nested_filter: true
end

The option is consumed before Mongoid validates association options, then retained on the association reflection for Graphoid schema generation.

# Generated because Sheet#project opted in
sheets(where: { project: { id_not: null } }) {
  data { id }
}

# Rejected because Attachment#record has no opt-in
attachments(where: { record: { id_not: null } }) {
  data { id }
}

Unflagged relations, including _some, _none, and _every collection filters, remain absent from generated input types. Selected relation fields retain order, limit, and skip, but do not expose where.

Checks ☑️

• relation_filter_restrictions_spec.rb: 6 examples, 0 failures
• Validates an opted-in belongs_to relation filter
• Validates unflagged to-many filters and selected-relation where are rejected
• Ruby syntax and git diff --check pass

[GiuseppeXD]

Before graphoid added every Mongoid association to the generated filter inputs.

input AttachmentFilter {
  record: RecordFilter
}

input RecordFilter {
  attachments_some: AttachmentFilter
  attachments_none: AttachmentFilter
  attachments_every: AttachmentFilter
}

Now, graphql-ruby rejects these during static schema validation:

attachments(where: { record: { id_not: null } }) {
  data { id }
}

InputObject 'AttachmentFilter' doesn't accept argument 'record'

[GiuseppeXD]

No longer executes or validates

records {
  data {
    attachments(where: { type: "picture" }) {
      id
    }
  }
}

However, other operations are still viable

records {
  data {
    attachments(limit: 10, skip: 0, order: { id: ASC }) {
      id
    }
  }
}

[niltonvasques]

Instead remove the feature from graphoid, lets toggle on/off with an attribute.

In postman this feature is useful in specific situations: records { where: { sheet: { key: "...." }} or sheets: { project: { name: "test"

[GiuseppeXD]

This tells Mongoid to allow the new type of param in the association