Migrate Cloudinary Integration to the Frontend

[bhuelsman]

Description:
Right now we are currently sending the images to backend, and then forwarded to Cloudinary for storage. Only the Cloudinary URLs are persisited in our databse.

Whats wrong with it?

• network overhead: the images are transmitted twice, mobile->backend, then backend->cloudinary. With large or hi-res images it can be slow and costly (esp on mobile data)
• Backend load: backed acts as proxy, which holds images in memory temporarily, which cna strain resources if many uploads happen simultaneously.
• Scalability: as app grows, it can lead to bottlnecks or higher server costs

How can we fix it?

• upload the images directly from the mobile app to Cloudinary (using Cloudinary's SDK or API) and then send only the resulting URLs to your backend. This would reduce network traffic, offfload processing, and minimize backend complexity. Cloudinary supports direct uploads from mobile apps (e/g/ via their react Native SDK or REST API
  URLs in the issue creation request instead of raw files