refactor(dev-env): use isContainerRunning for import and sync commands

[sjinks]

Description

This pull request refactors the code to check if the development environment is running before importing SQL data. Instead of checking if the whole environment is up, it now specifically checks if both the php and database containers are running. Additionally, it introduces a new utility function to check the running status of individual containers and updates imports accordingly.

Improvements to environment status checks:

• Replaced the broad isEnvUp check with explicit checks for the php and database containers using the new isContainerRunning function in DevEnvImportSQLCommand. This ensures a more accurate validation of required services before proceeding.

New utility function:

• Added isContainerRunning to dev-environment-lando.ts, which checks if a specific container for a given environment is running by querying Docker directly.

Code cleanup and import updates:

• Updated imports in dev-env-import-sql.ts and dev-environment-lando.ts to remove unused functions and add the new utility where needed. [1] [2]

Changelog Description

Changed

• The environment status checks for vip dev-env import sql and vip dev-env sync sql commands now verify that the PHP and Database containers are running, rather than checking the status of the entire environment.

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

vip dev-env create --slug test-is-up < /dev/null
vip dev-env start --slug test-is-up
docker stop testisup-nginx-1 # or whatever the container is called
vip @app.env dev-env sync sql

Without this patch, synchronization will fail with the "Environment needs to be started first" message. With this patch, it will succeed.

[github-actions]

Dependency Review

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

Scanned Files

None

[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

[Copilot]

Pull Request Overview

This pull request refactors the development environment status checks for SQL import and sync commands to be more specific and accurate. Instead of checking if the entire environment is up, it now verifies that only the required containers (PHP and database) are running before proceeding with operations.

• Replaces broad isEnvUp checks with specific container status validation
• Introduces a new isContainerRunning utility function for granular container status checking
• Updates import statements to remove unused functions and add new utilities

Reviewed Changes

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

File	Description
src/lib/dev-environment/dev-environment-lando.ts	Adds new isContainerRunning function to check individual container status via Docker API
src/commands/dev-env-import-sql.ts	Replaces isEnvUp with specific PHP and database container checks using the new utility function