A variety of changes

[geekygirlsarah]

What GitHub issue does this PR apply to?

Resolves #685

What changed and why?

• Rename thesaurus languages to entries
• (wip) Move language files to a langs/ directory
• Add initial alterations to make a SQL/NoSQL section happen, some sample entries too
• Add CodeQL and security checkers, optimize other CI/CD
• Add comprehensive test coverage for commands, generators, middleware, models, and views
• Refactor template generation, update error handling, and clean up meta info configuration
• Add AGENTS.md for anyone that wants to use AI on this project
• Add guidelines for AI tool usage in contributions
• Enhance CI/CD workflows: add Dependabot configuration, improve job concurrency, and pin action versions for stability
• Fix borked merge between CT main and my fork
• Upgrade to Django 6.1 and Python 3.14
• Refactor email and logging configurations
• Switch from django-on-heroku to dj-database-url and whitenoise for enhanced static file handling and deployment
• Replace management command external calls with internal calls
• Add OS path safety check in ThesurausEntry loading
• Add OS path safety check (now OS agnostic) in ThesurausEntry loading

AI bots used in the process of making this PR

JetBrains Junie, OpenCode Big Pickle

(If editing website code) Please add screenshots

Checklist

• I claimed any associated issue(s) and they are not someone else's
• I have looked at documentation to ensure I made any revisions correctly
• I tested my changes locally to ensure they work
• For language files, I have validated the edited files are valid JSON and data shows up correctly
• For website code edits, I have added or edited any appropriate unit tests for my changes
• If I used artificial intelligence (AI), I have reviewed the suggested changes and ensured they work correctly

Any additional comments or things to be aware of while reviewing?

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.