[PLTFRM-1781] Set memory limit for Elasticsearch to 1GB

[rinatkhaziev]

Description

Elasticsearch's default behavior is to claim 50% available memory, which is undesirable. This PR introduces hard cap of 1GB.

It can be overridden via the .lando.local.yml, like so

services:
  elasticsearch:
    services:
      deploy:
        resources:
          limits:
            memory: 1GB

Changelog Description

Changed

• Local Dev Env: Elasticsearch container memory is capped at 1GB now

Pull request checklist

• Update SETUP.md with any new environmental variables.
• Update the documentation.
• Manually test the relevant changes.
• Follow the pull request checklist
• Add/update automated tests as needed.

New release checklist

• Automated tests pass.
• The Preparing for release checklist is completed.

Steps to Test

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[Copilot]

Pull Request Overview

This PR sets a hard memory limit of 1GB for the Elasticsearch container to prevent it from consuming excessive resources (50% of available memory by default). The change also removes the experimental label from PHP 8.4 and bumps the development environment version.

• Added memory limit configuration for Elasticsearch container
• Updated PHP 8.4 label from experimental to stable
• Bumped dev environment version to 2.3.1

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
assets/dev-env.lando.template.yml.ejs	Added deploy configuration with 1GB memory limit for Elasticsearch service
src/lib/constants/dev-environment.ts	Removed experimental label from PHP 8.4 and incremented version number

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rinatkhaziev]

This seems like a sane default value but probably it may not be enough for larger apps.