[Misc][Chore] Clean Up AsyncOutputProcessing Logs

[robertgshaw2-redhat]

SUMMARY

• This should not be a warning on V1
• Remove warnings about lack of async output processing when disabled

[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.

🚀

[njhill]

Thanks @robertgshaw2-redhat I'd also noticed that but then forgot about it!

Should we still log these in the V0 case though?

[robertgshaw2-redhat]

@njhill - I think that a warning is unnecessary.

It is disabled with:

• --enforce-eager ... i.e. the user is already making a choice to not get best perf
• platforms we do not support it on