[Chore] remove unused jinaai_serving_reranking

[Abirdcfly]

No description provided.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[DarkLight1337]

Could you elaborate? Which PR made this unused?

[Abirdcfly]

Could you elaborate? Which PR made this unused?

maybe #12846 renamed jinaai_serving_reranking to openai_serving_scores?

[DarkLight1337]

Hmm, let's rename it to serving_scores instead of openai_serving_scores to be less misleading

[Abirdcfly]

Hmm, let's rename it to serving_scores instead of openai_serving_scores to be less misleading

It seems my screenshot may have caused confusion.

The point I intended to convey was that there's a single definition for jinaai_serving_reranking that is not used, and it should be removed.

As for the naming of openai_serving_scores, I suspect it's due to the presence of other related variables in the same class, such as
openai_serving_models,
openai_serving_chat,
openai_serving_completion,
openai_serving_pooling,
openai_serving_embedding,
openai_serving_classification,
openai_serving_tokenization,
openai_serving_transcription.

[DarkLight1337]

That's because the other APIs follow OpenAI API. However, this one does not, so I think it's better to have a different name for it to avoid confusion.