Compare SearchResult values instead of hashes in eql?

[OskarEichler]

Summary

Compare ordered array contents and modseq in SearchResult#eql? instead of treating matching hash values as proof of equality. Also reject a non-nil modseq when the receiver has no modseq. The existing order-insensitive == and hash calculation are unchanged.

Reproduction

require 'net/imap'
a = Net::IMAP::SearchResult[1, modseq: nil]
b = Net::IMAP::SearchResult[1, modseq: 2]
p [a.eql?(b), b.eql?(a)] # before: [true, false]; after: [false, false]
colliding = Class.new(Net::IMAP::SearchResult) { def hash = 7 }
p({colliding[1, modseq: 2] => :a, colliding[9, modseq: 3] => :b}.size)
# before: 1; after: 2

Verification

• 400 focused checks; 73 failing expectations before, zero afterward. They cover nil/non-nil modseq, ordered contents, plain arrays, subclasses, deliberately colliding hashes and Hash lookup. Related merged 🐛 Fix SearchResult#== for LHS with no modseq #514 fixed ==, not eql?.
• Existing rake test on this isolated branch: 1726 tests, 12588 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications, Ruby 4.0.6 via rbenv. The baseline also passes all 1,726 tests; assertion counts vary slightly across runs.
• Supplemental RuboCop Lint retains the same 48 existing findings. Ruby syntax and git diff --check pass. No repository tests, dependencies or workflows were added or modified; focused reproductions live outside the repository under the consumer's no-new-tests policy.
• Independent branch based on 6d2ef7a636a1e2449187a83b06ac7a5baa54ead2; the runtime diff from released 0.6.6 is documentation-only before this patch.

Compatibility and limits

No API, dependency or Ruby-minimum change. Distinct values no longer collapse into one Hash key. Nil-modseq Array compatibility and the non-nil same-class restriction remain. Plain Array receivers still use Array equality; this does not promise cross-class symmetry for arbitrary Array subclasses. Other Ruby/OS versions were not run locally. No production or external IMAP service was used. Local verification does not imply upstream CI approval or comprehensive behavioral coverage.