- Default RELAY_VERSION to empty; when unset, resolve the latest stable
  release from https://builds.r2.relay.so/meta/latest instead of pinning 0.9.1.
- Download the Relay build matching the host architecture by deriving the
  suffix from `uname -m` (x86_64 -> x86-64, aarch64 stays aarch64).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…uild

- Bump the base image to ":3" (Amazon Linux 2023 — glibc 2.34, OpenSSL 3) and
  enable the layer for PHP 8.2-8.5 in config.json (it was empty, so the layer
  was never built or published).
- Switch from Relay's "centos7" build to its "el9" build, which links the
  system OpenSSL 3 / glibc already shipped by the AL2023 base image and the Bref
  runtime.
- Drop the custom OpenSSL 1.1 compilation (and CA bundle). It existed only
  because the old centos7 build needed OpenSSL 1.1; the el9 build uses the
  system libssl.so.3 / libcrypto.so.3, which copy-dependencies bundles into the
  layer. This also removes the slowest step of the build.

Verified locally with `make test layer=relay php_versions=85`: the extension
loads on the bref/php-85 runtime, \Relay\Relay is available, and `php -v` is
clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Relay is built for PHP 8.2-8.5, so relay-php-81 doesn't exist. Use the
lowest built version (matching e.g. the Oracle oci8-php-83 row).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

upgrade the bsdiff extension to v0.2.1, with PHP 8.5 support added

…-to-1.20.0

Update Datadog layer to use dd-trace-php v1.20.0

Update Blackfire extension

…g-layer-to-1.20.0

Revert "Update Datadog layer to use dd-trace-php v1.20.0"

relay: latest version by default, arm64-ready, build on AL2023 + OpenSSL 3