refactor(storage): remove legacy upload filesystem

[AmzBG]

Description

• Remove the legacy /uploads static-file route from the API now that production media has been migrated to object storage.
• Stop creating profile-picture and project-media directories in the production Docker image.
• Remove the tracked upload-directory placeholder from the repository.
• Keep legacy local upload paths ignored so existing local media cannot be committed accidentally.

Link to issue or ticket

N/A

Steps to QA

1. Confirm the production media migration dry run reports zero legacy records.

2. Build the application with npm run build and confirm both the API and web production builds succeed.

3. Start the API with the object-storage environment variables configured and confirm it starts without creating an apps/api/uploads directory.

4. Upload a profile picture and project media, then confirm the files are written to object storage and their public URLs use the configured CloudFront domain.

5. Run the automated checks:

   • npm test --workspace=api -- --runInBand
   • npx turbo run lint
   • npx turbo run check-types
   • npm run format:check

Screenshots

N/A