All services: clean up compose comments and rename compose.yml to compose.yaml

[jackspiering]

What changed

Two things, in three commits. Neither changes a setting, value, or structure.

1. Comments and whitespace

In the service template's compose.yaml and in every service that carries the same lines.

Change	Before	After	Services
Ports comment	# Binding port ${SERVICE}PORT to the local network - …	# Binding the service port to the local network - …	100
Ports comment, other variant	# Binding port ${SERVICEPORT} to the local network - …	same as above	3
Network comment	# Sidecar configuration to route ${SERVICE} through Tailscale	# Sidecar configuration to route the service through Tailscale	111
Block heading	# ${SERVICE}	# Application	110
Header line	# All the ${ xx } need to be defined there.	# Every variable used in this file must be defined there.	122
DNS block	# dns: and # - ${DNS_SERVER}	#dns: and # - ${DNS_SERVER}, as in the template	47
Trailing whitespace	present	removed	103
EXAMPLE_VAR comment	indented five spaces	indented six spaces	1 (Transmute)

The template gets every change except the two variants it never had.

Kaneo has three headings of the form # ${SERVICE} - DB. They are now # Database, # Backend (API), and # Frontend (Web).

2. compose.yml renamed to compose.yaml

The template and 116 services use compose.yaml. These six used compose.yml and are renamed: AFFiNE, EspoCRM, File Browser, Paperless, RustDesk Server, and XWiki. The file contents are the same apart from the comment changes above.

A comment in Mattermost's .env still called the stack's file docker-compose.yml. It now says compose.yaml.

Why

Compose does not interpolate variables inside comments, so ${SERVICE} stays literal text there. ${SERVICE}PORT in the ports comment is a find-and-replace artifact that 100 services copied from the template.

The DNS block existed in two spellings, and trailing whitespace makes git diff --check fail on any later edit of those lines.

One file name for every service matches the template and lets scripts and checks address compose.yaml everywhere. Compose finds both names, so docker compose up works as before. Someone who passes the file by name, such as docker compose -f compose.yml up, must use the new name after pulling.

Not in this PR

• Variables inside commented-out code, such as # - ./${SERVICE}-data/app/config:/config, and in the health-check guidance that quotes pgrep -f ${SERVICE} as a command. Those are code, not prose.
• The indentation of the two header lines under services:.
• Anything that changes behaviour. Follow-up PRs will cover those.

Testing

• The output of docker compose config is identical before and after this change for all 122 services and the template. I saved the resolved configuration of each directory on main and on this branch and compared them with diff -r. The 7 services with required variables and the template got placeholder values for this comparison.
• The same comparison for the rename: identical output before and after for the six renamed services, and docker compose config --quiet passes in each.
• No README or other file in the repository refers to compose.yml of these services. No other .env or compose file calls its stack's file docker-compose.yml.
• git diff --check passes.
• No trailing whitespace is left in any compose file.

Not tested: I did not start the stacks, because the resolved configuration is unchanged. No Markdown file changed, so I did not run rumdl.