#34 Sentiment Analysis Backend

[BasicallyOk]

What does this PR do?

Providing the solution to #34 mainly. The experiences will be evaluated and changed over time as more submissions are added. Allowing users to find out how many people shares similar experiences as them. Also allow researchers a way to identify trends.

The ticket will also include a script to seed the database with Erowid submissions. This is clutch for testing analytics and researcher-centric functionalities.

Github Issue Number

Resolves: #34 #68 #71 #72 (turns out I can get it done pretty quick)

Relates to: Potentially #72, but that ticket will probably warrant its own PR due to the size of the rework involved.
#69 (nice, but I forgot about it, not nice, next pr it is)

Author checklist

If any of these points have yet to be satisfied, make sure that you set the title to the format DRAFT #issue-num Title

• The title is short and descriptive of the PR. Must start with the Github Issue Number (format: #issue-num Title).
• The description follows proper cl description practices and mentions related Github Issues (make sure this is the first thing you mention).
• Branch has merged in the latest version of main
• Linting has occured, as per the project linting config
• All changed functions have proper docstring/wiki updates (front-end team) to describe what they do and how to use them.
• Add yourself as the assignee.
• Add reviewer a reviewer and let them know on discord.
• Ensure that all relevant ticket has been linked to the PR

Reviewer checklist

• Relevant issue is mentioned in description
• Code solves the issue
• Code follows the specification
• Code is the best solution for the issue
• Branch is ahead of main
• Ensures the fix/feature works locally (docker compose up --build)

[mustafa-tariqk]

address changes and we should be good to go. I hate you for making this PR so huge

[mustafa-tariqk]

what is this file? does it need to exist?

[mustafa-tariqk]

do we need this file as well?