fix(nginx): Remove static file extension location block

[nfebe]

This block serves files matching static extensions directly from disk, bypassing PHP. Any Laravel API route ending in .png, .jpg, etc. never reaches the application — breaking file-serving endpoints and CORS middleware.

Redundant since try_files already serves static files from disk.

[sourceant]

Code Review Summary

The PR removes a regex-based location block in Nginx that was intercepting requests for common static file extensions. This fixes a bug where Laravel routes mimicking these extensions (e.g., dynamic image generation or protected file downloads) were returning 404s from Nginx instead of being handled by PHP.

🚀 Key Improvements

• Fixed routing for dynamic assets: Laravel endpoints ending in .png, .js, etc., will now correctly reach the application.
• Simplified configuration: Removed redundant logic that is usually handled by try_files.

💡 Minor Suggestions

• Consider re-implementing Cache-Control headers in a way that doesn't break routing.

[sourceant]

Review complete. See the overview comment for a summary.

[sourceant]

While removing the extension block solves the routing issue, you've lost the browser caching headers (Expires, Cache-Control) for your actual static assets. Consider moving these headers into a general location block or adding them to your main location / if you want to maintain performance for real static files.

Suggested change

	add_header X-Frame-Options "SAMEORIGIN" always;
	location / {
	try_files $uri $uri/ /index.php?$query_string;
	# Re-add caching for static assets here or in a more specific way that doesn't intercept PHP
	}
	add_header X-Frame-Options "SAMEORIGIN" always;
	add_header X-Content-Type-Options "nosniff" always;
	add_header X-XSS-Protection "1; mode=block" always;