[Quantization] Pool model support bitsandbytes

[jeejeelee]

Test snippet

from vllm import LLM
from vllm.config import PoolerConfig
query = "who are tyout"
prompts = [
    f"query: {query}</s>",
    f"passage: {query} {query}</s>",
]
pooler_config = PoolerConfig(pooling_type="LAST", normalize=True)
model = LLM(
    model="intfloat/e5-mistral-7b-instruct",
    task="embed",
    enforce_eager=True,
    quantization="bitsandbytes",
)

outputs = model.embed(prompts)

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

Is there any existing model we can use to test this?

[jeejeelee]

_ No description provided. _

Is there any existing model we can use to test this?

We can use intfloat/e5-mistral-7b-instruct, I have updated the test snippet in the top comment

[DarkLight1337]

Can you add this test to the CI?

[jeejeelee]

The reason I didn't add it was due to concerns about CI pressure. If you think related tests should be added, I'll implement it ASAP.

[DarkLight1337]

The quantization model test is conditional so it should be fine to add it

[jeejeelee]

This change is to avoid the warning below

The `load_in_4bit` and `load_in_8bit` arguments are deprecated and will be removed in the future versions. Please, pass a `BitsAndBytesConfig` object in `quantization_config` argument instead

[jeejeelee]

The quantization model test is conditional so it should be fine to add it

I have added the test @DarkLight1337

[DarkLight1337]

Thanks

[jeejeelee]

It looks like we need to force merge