AAP-58583: SaaS Ansible Chatbot does not find information from RAG DB

[romartin]

Jira Issue: https://issues.redhat.com/browse/AAP-58583

Description

Fixes:

• Prevents from overriding the chatbot image entry-point
• Used the python executable reference from the venv, instead of container's /usr/bin

Production deployment

• This code change is ready for production on its own
• This PR should be released in 2.4 (cherry-pick should be created)
• This PR should be released in 2.5 (cherry-pick should be created)
• This PR should be released in 2.6 (cherry-pick should be created)
• This code change requires the following considerations before going to production:

[romartin]

@ldjebran this works for upstream, I tested it, BUT I am afraid if it may BREAK downstream once mirroring the repo, as I think the downstream chatbot image does not have the new provider_rag.env file which this PR assumes to be present in the image. I think downstream image actually just exports directly the PROVIDER_VECTOR_DB_ID itself....

[ldjebran]

The downstream image has the file

cat /.llama/data/distributions/ansible-chatbot/provider_rag.env 
PROVIDER_VECTOR_DB_ID=vs_cef6882e-00f4-4f26-b130-6a4a1bf15553
bash-5.1$ 

[ldjebran]

LGTM