feat(supported-version): add Mage-OS 3.5.0 (Magento 2.4.9)

[rhoerr]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/mage-os/github-actions/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

The supported-version matrix tops out at Mage-OS 3.4.0 (released 2026-08-11),
which is still marked as the current release with an EOL of 2029-08-11. Mage-OS
3.5.0 is a security release publishing 2026-09-08 and has no matrix entry, so CI
has no service configuration for it and currently-supported / latest /
next resolution would continue to point at 3.4.0.

Fixes: N/A

What is the new behavior?

Adds Mage-OS 3.5.0 (upstream Magento 2.4.9), releasing 2026-09-08 with an EOL of
2029-09-08:

• individual.json — new mage-os/project-community-edition:3.5.0 entry;
  the preceding 3.4.0 entry is set to EOL on the 3.5.0 release date
  (2026-09-08), per the established same-day supersede convention.
• composite.json — new >=3.5 <3.6 range entry; >=3.4 <3.5 EOL moved to
  2026-09-08; the default (mage-os/project-community-edition) and :next
  entries rolled forward to the 3.5.0 release/EOL dates.
• get-currently-supported.spec.ts — new assertion that 3.5.0 is the sole
  currently-supported version as of 2026-09-08T00:00:01Z.
• dist/index.js — rebuilt via npm run build.

Service requirements are carried over unchanged from 3.4.0. 3.5.0 is a security
release against the same upstream Magento 2.4.9 certified stack, so no service
versions move:

PHP	8.4
Composer	2.10.2
MariaDB	mariadb:11.4
OpenSearch	opensearchproject/opensearch:3
RabbitMQ	rabbitmq:4.1-management
Valkey	valkey/valkey:8
Varnish	varnish:7.7
Nginx	nginx:1.28
OS	ubuntu-latest

npm test passes: 123 tests across 12 suites. The newly added case was
confirmed to execute in isolation (npx jest -t "2026-09-08T00:00:01Z" →
1 passed, 122 skipped) rather than relying on the aggregate pass count, which
also confirms 3.4.0 correctly drops out of the supported set on that date.

Does this PR introduce a breaking change?

• Yes
• No

Only additive matrix data plus the routine EOL roll-forward of the superseded
3.4.0 line. Workflows pinned to an explicit older version are unaffected; those
tracking latest / next / the bare package name will pick up 3.5.0, which is
the intended behavior on release day.

Other information

Follows the same structure as the 3.4.0 addition (#388) and 3.3.0 (#387).

This branch is based on current main (post-#370), so the 3.x entries carry
mariadb: mariadb:11.4 rather than the mysql key used before MariaDB was
modeled as a separate service — the new 3.5.0 entry and >=3.5 <3.6 range
inherit that shape directly from 3.4.0 as it now stands.

🤖 Generated with Claude Code

https://claude.ai/code/session_017jN6uxRhypp6cNB6KWp9Wy

[damienwebdev]

Lgtm