chore: small consistency and documentation fixes

[erimicel]

A handful of unrelated small fixes that don't really warrant individual PRs.

AnalyticsRules#[] and CurationSets#[] now memoize

Every other resource collection in the gem caches its proxy on first [] access — Collections, Documents, Aliases, Keys, Presets, Synonyms, SynonymSets, NlSearchModels, StemmingDictionaries, Overrides, CurationSetItems, AnalyticsRulesV1. AnalyticsRules and CurationSets were the only two that built a fresh wrapper on every call.

client.curation_sets['x'].equal?(client.curation_sets['x'])
# before: false
# after:  true

This is purely a consistency fix — there was no shared mutable state on the proxies, so the previous behaviour wasn't a bug, just surprising.

Drop unreachable || 3 fallback in Configuration#num_retries

@num_retries = options[:num_retries] || (@nodes.length + (@nearest_node.nil? ? 0 : 1)) || 3

The LHS is always a positive integer — validate! raises before we get here if @nodes is empty — so || 3 can never fire. Just deletes the dead tail.

Drop node.send(:[], attr) in node_missing_parameters?

%i[protocol host port].any? { |attr| node.send(:[], attr).nil? }
# →
%i[protocol host port].any? { |attr| node[attr].nil? }

Same behaviour, less indirection.

README: document Typesense::Error#data

Typesense::Error exposes a .data reader that holds the underlying Faraday response, but the README didn't mention it. Adds a short error-handling section showing how to pull the status / body off a raised exception, plus the list of status-code-to-class mappings.

Tests

• bundle exec rspec spec/typesense/configuration_spec.rb spec/typesense/analytics_rules_spec.rb spec/typesense/curation_sets_spec.rb — all green.
• bundle exec rubocop on the touched files — no offences.

PR Checklist

• I have read and signed the Contributor License Agreement.

[tharropoulos]

Looks like some tests are failing