Add llama2 llm

[ErdemOzgen]

• Added ollama with docker container
• GPTVulnerabilityReportGenerator : Retrieves an OpenAI API key and sets the model to 'gpt-3.5-turbo'. If the API key is not available, it initializes an Ollama instance for local use.
• GPTAttackSuggestionGenerator: Similar to the GPTVulnerabilityReportGenerator, it retrieves an OpenAI API key and sets the model to 'gpt-3.5-turbo', or initializes an Ollama instance if the API key is not available.
• Changed makefile make up and make down sections.
• After docker container up it will run command to pull llama2-uncensored llm model and serve model.

This PR fixes #1035.

[ErdemOzgen]

Based on my understanding, the two failed GitHub Actions are facing distinct issues. The problem does not pertain to a Pull Request (PR). The issue with pulling the Docker image is due to an Error: Username and password required. Meanwhile, the Auto Comment action is encountering a different problem, which could potentially be resolved by ensuring that the GitHub token being used has the appropriate permissions.

[AnonymousWP]

Uhm, I compared with #1096, but what's the difference? I can't spot any difference when I tried to compare it using the GitHub feature.

[AnonymousWP]

Based on my understanding, the two failed GitHub Actions are facing distinct issues. The problem does not pertain to a Pull Request (PR). The issue with pulling the Docker image is due to an Error: Username and password required. Meanwhile, the Auto Comment action is encountering a different problem, which could potentially be resolved by ensuring that the GitHub token being used has the appropriate permissions.

Would you be able to fix this by a new PR? I understand some can't be fixed due to insufficient permissions, though.

[ErdemOzgen]

Based on my understanding, the two failed GitHub Actions are facing distinct issues. The problem does not pertain to a Pull Request (PR). The issue with pulling the Docker image is due to an Error: Username and password required. Meanwhile, the Auto Comment action is encountering a different problem, which could potentially be resolved by ensuring that the GitHub token being used has the appropriate permissions.

Would you be able to fix this by a new PR? I understand some can't be fixed due to insufficient permissions, though.

@AnonymousWP You can check this PR
Also fetch my current PR; needs to workflow approval again.

[psyray]

This need to be tested, @yogeshojha You could test it ?

[yogeshojha]

Hi @ErdemOzgen,

Thank you for the excellent work.

I am closing this as I have already merged your changes through this MR
#1259

Thanks