Integration With PEP8 Formatting and a Logger Wrapper Function

[exowanderer]

• Please check if the PR fulfills these requirements

• [x] The commit message follows our guidelines

• [x] Tests for the changes have been added (for bug fixes/features)

• [x] Docs have been added / updated (for bug fixes / features)

• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) This is a maintainability update with

• ollama model and URL as environment variables

• PEP8 formatting for variable names

• multi line usage for multi-kwarg function calls

• new logger.py for print, warning, error, and debug messages

• streamlined formatting for list comprehension

• re-introduced stablem2 model because the openchat does not run on our "test server" aka, my laptop

• rag_pipeline is now a function call living in the rag.py file instead of the api.py

• Fronted UI calls "/api?query=" to avoid single letter variable names. Some downstream formatting had to be changed.

• What is the current behavior? (You can also link to an open issue here)

• ollama model and URL as hard coded values

• PEP8 violations

• multi-kwarg function calls on a single line

• print to stdout as manual "logging"

• for loops with print statements instead of list or dictionary comprehension

• using openchat because our cloud system has a gpu

• Fronted UI calls "/api?q="

• What is the new behavior (if this is a feature change)?

• logger.py is a completely new functionality

• rag.py has been re-invigorated to host the rag_pipeline (taken out of api.py)

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) No breaking changes

• Other information:

New Feature Submissions:

1. [x] Does your submission pass tests?
2. [ ] Have you lint your code locally before submission?

Changes to Core Features:

• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ] Have you written new tests for your core changes, as applicable?
• [x] Have you successfully run tests locally with your changes?