[LoRA][Kernel] Remove the unused libentry module

[jeejeelee]

vLLM's current Triton version is 3.1.0, it's safe to remove the libentry module. See: #5036 (comment)
ping @DarkLight1337

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
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 do one of these:

• Add ready label to the PR
• Enable auto-merge.

🚀

[DarkLight1337]

The triton version doesn't appear to be specified for all vLLM backends.

[jeejeelee]

The triton version doesn't appear to be specified for all vLLM backends.

The current triton in vLLM comes from PyTorch, so it might be safe to remove it.

[DarkLight1337]

Can you point to where I can find that information?

[jeejeelee]

Can you point to where I can find that information?

See: #4061

[DarkLight1337]

I see, thanks. In that case let's merge this.

[jeejeelee]

I see, thanks. In that case let's merge this.

Thanks.
On one hand, libentry indeed doesn't have much use for the current vllm anymore.
Another reason is that libentry has a potential risk that prevents triton kernels from completing multi-GPU testing, which means we cannot verify whether issues like #9794 can be resolved.