RUBY-3445 Add timeouts in OpMsg instead of Protocol::Message

[jamis]

Per RUBY-3445:

One of the challenges with the cursor work is that both the find and getMore commands have non-standard behaviors regarding timeouts. Currently, the maxTimeMS option is being set identically for every command, on the Protocol::Message class. In order to support per-command timeout behaviors, we need to move that to the OpMsg subclasses themselves.