Update Supabase default template to modern `compose.yml` standards.

What problem will this feature address?

The current Supabase template in Dokpoly uses the legacy docker-compose.yml format and older configurations. This can lead to compatibility issues with newer Docker Engine features and deviates from the current Supabase self-hosting documentation, making it harder for users to maintain or customize their stacks.

Describe the solution you'd like

I would like to see the Supabase default template updated to use the standard compose.yml filename. Additionally, the service definitions should be aligned with the latest Supabase Docker repository to ensure users are getting the most stable and feature-rich version of the stack out of the box.

Describe alternatives you've considered

The current workaround is manually editing the YAML files after deployment or creating a custom template, but this defeats the purpose of having a "one-click" default template in Dokpoly.

Additional context

Updating this will bring Dokpoly's Supabase integration in line with modern container best practices and reduce "configuration drift" for new users.

Will you send a PR to implement it?

I would prefer the maintainers or someone more familiar with the Dokpoly template engine to handle the implementation to ensure it meets the project's standards, but I am happy to help test it!

Locate Dokploy's default Supabase template and compare its docker-compose.yml with the current compose.yml and service definitions in the linked Supabase Docker repository. First inspect how the template engine loads and deploys this configuration, then validate that a new one-click Supabase deployment uses the updated filename and services without manual edits.