Summary

This PR fixes a common build failure in the workspace container caused by upstream Ubuntu PPA metadata changes (ReleaseInfo changes).
It introduces a new environment variable WORKSPACE_ALLOW_RELEASE_INFO_CHANGE (default: false) to optionally allow APT to accept suite/label changes without manual intervention.

• The fix is backward-compatible and opt-in.
• There is no side effect on existing users unless they explicitly enable the new variable.

Problem

When building the workspace container, users may encounter APT errors regarding repository metadata changes:

E: Repository 'http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease' changed its 'Label' value from '***** The main PPA for supported PHP versions with many PECL extensions *****' to 'PPA for PHP'

This problem occurs more frequently after upgrading to newer operating systems such as macOS Sequoia 15.4.1, due to stricter base image validations or upstream repository changes.
However, it is not specific to macOS — it can happen on any OS whenever Ubuntu-based repositories modify their metadata.

Root Cause

• Ubuntu PPAs occasionally update their "Label" or "Suite" fields.
• APT treats these changes as potential security risks and blocks further installs.
• Since Docker builds are non-interactive, APT cannot prompt for confirmation and fails immediately.

Proposed Fix

• Add a new .env variable: WORKSPACE_ALLOW_RELEASE_INFO_CHANGE.
• If set to true, dynamically pass the --allow-releaseinfo-change flag to apt-get update during build time.
• If set to false (default), APT behaves normally without accepting release info changes.

How it Works

• Added ARG WORKSPACE_ALLOW_RELEASE_INFO_CHANGE and ENV WORKSPACE_ALLOW_RELEASE_INFO_CHANGE in the workspace Dockerfile.
• Inside the build RUN block, the script checks the value of this environment variable.
• If enabled, the --allow-releaseinfo-change flag is appended to the apt-get update command.
• This avoids build-time failures without modifying global system configurations (like /etc/apt/apt.conf.d/).

Benefits

• Workspace builds succeed automatically even when PPAs update metadata.
• No need for manual Dockerfile edits or intervention.
• Safe, optional, and minimal change to existing behavior.
• Fully environment-driven, respecting Laradock's conventions.

Checklist

• Fully backward-compatible
• Minimal code surface
• No runtime impact
• No security weakening unless explicitly enabled
• Controlled via environment variable
• Tested with both WORKSPACE_ALLOW_RELEASE_INFO_CHANGE=true and false
• Tested on both Intel and Apple Silicon (M1/M2) macOS systems

Suggested Documentation Update

Add this line into the workspace section of .env.example:

### Allow APT to accept release info changes if PPAs change metadata (Ubuntu PPA compatibility)
WORKSPACE_ALLOW_RELEASE_INFO_CHANGE=false