Clarify Primary Dependency Management Tool in `pyproject.toml`

**Issue Description:**

The `pyproject.toml` file for the "llm_vm" project currently includes configurations for both Poetry and Setuptools as potential dependency management tools. This setup may lead to confusion among contributors and users. This issue aims to clarify the choice of the primary dependency management tool for this project.

**Proposal:**

1. **Choose a Primary Tool:** We should decide whether Poetry or Setuptools will serve as the primary dependency management tool for the "llm_vm" project. Having a single primary tool simplifies the development process and avoids potential conflicts.

2. **Update the Configuration:** Once a decision is made, update the `pyproject.toml` file to reflect the choice. Remove or comment out any sections related to the tool that won't be used as the primary one.

3. **Document the Choice:** In the project's documentation or README, we should clearly state which dependency management tool is being used as the primary one. Provide instructions on how contributors and users should interact with it.

**Discussion:**

- Are there specific reasons for using both Poetry and Setuptools in the same file for this project?
- What benefits or advantages does each tool bring to the "llm_vm" project?
- Are there any potential drawbacks or conflicts in using both tools simultaneously?

This issue is intended to ensure clarity and consistency in managing dependencies for the "llm_vm" project. Please share your thoughts and suggestions regarding the choice of the primary dependency management tool.

Thank you for your input!