Fix: Add NamedWriteable for RuleQueryRankDoc

[kderusso]

Resolves #126071

Adds a NamedWriteable entry for RuleQueryRankDoc.

This failure isn't reproduceable in main with the given test script, but still occurs in Serverless, with failures such as the following:

"failures": [
      {
        "shard": 0,
        "index": "index-002",
        "node": "NA_btEkhTxKytf_u2V8LRQ",
        "reason": {
          "type": "illegal_argument_exception",
          "reason": "Unknown NamedWriteable [org.elasticsearch.search.rank.RankDoc][query_rule_rank_doc]"
        }
      },
      {
        "shard": 2,
        "index": "index-001",
        "node": "NA_btEkhTxKytf_u2V8LRQ",
        "reason": {
          "type": "illegal_argument_exception",
          "reason": "Unknown NamedWriteable [org.elasticsearch.search.rank.RankDoc][query_rule_rank_doc]"
        }
      }
    ]

[elasticsearchmachine]

Pinging @elastic/search-eng (Team:SearchOrg)

[elasticsearchmachine]

Pinging @elastic/search-relevance (Team:Search - Relevance)

[elasticsearchmachine]

Hi @kderusso, I've created a changelog YAML for you.

[Mikep86]

Should we also backport to 8.17?

[elasticsearchmachine]

💔 Backport failed

Status	Branch	Result
❌	8.19	Commit could not be cherrypicked due to conflicts
❌	8.17	Commit could not be cherrypicked due to conflicts
❌	8.18	Commit could not be cherrypicked due to conflicts
❌	9.0	Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 128153

[kderusso]

💚 All backports created successfully

Status	Branch	Result
✅	9.0
✅	8.19
✅	8.18
✅	8.17

Questions ?

Please refer to the Backport tool documentation