DBC22-6080: Add Brotli/zstd compression to backend

[wmuldergov]

📝 Submitter

🔗 JIRA Ticket

• Ticket Link: https://moti-imb.atlassian.net/browse/DBC22-6080

---

✅ Quality Assurance & Requirements

• Requirements Met: I have confirmed that all acceptance criteria from the JIRA ticket are fulfilled.
• Tested desktop in local or dev envs
• Tested mobile in local or dev envs
• Ran unit tests locally
• SonarCloud: I have verified that the SonarCloud analysis is clean/passing for this branch.

🧪 How to Test (if required)

1. Open devtools
2. Confirm that the API's are using br for compression
3. Try run a few curl requests like these with different encoding types curl -v -X GET -H "Accept-Encoding: gzip, br" "https://dev.drivebc.ca/api/webcams/?" -o /dev/null
4. curl -v -X GET -H "Accept-Encoding: gzip, br, zstd" "https://dev.drivebc.ca/api/webcams/?" -o /dev/null
5. curl -v -X GET -H "Accept-Encoding: gzip" "https://dev.drivebc.ca/api/webcams/?" -o /dev/null
6. All should return the encoding you requested with zstd being first priority, br second and gzip 3rd.
7. Go to dev.drivebc.ca and confirm site and API's work as expected. Also try on mobile.

---

🔍 Reviewer Checklist

• Reviewed code for logic and cleanliness
• Re-tested desktop/mobile in local or dev envs
• Verified no new console warnings/errors
• Confirmed that any new env variables are understood/documented

[wmuldergov]

This will need some further work, due to new errors in the timelapse API discovered:
UnicodeDecodeError at /api/webcams/343/timelapse/20260417190009/
'utf-8' codec can't decode byte 0xff in position 0: invalid start byte

Update: Switched to a different package that also supports zstd, which seems to not cause this error.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud