CTHUB - General Error Log

**Describe the task**
General errors in CTHUB should print a stack trace of the error to the console so the issue can be properly looked into.

**Purpose**
When testing on dev, sometimes we run into testing issues with the general "There was an error uploading" message because it tells us very little; however most of the time that message is only displayed due to a technical error not a user error. So it would be helpful to see what is happening on the backend when a user encounters this error instead of trying to replicate it locally.

**Acceptance Criteria**
- [ ] Place error log(s) in critical areas of the CTHUB app.

Start by locating the CTHUB backend path that produces the general “There was an error uploading” message and review how errors are currently handled. Identify the critical areas requiring logging; the work is done when technical failures produce stack traces in the console without changing the user-facing error message.

Written by the indexing model from the issue text.