Set the mount path for vip-config to ABSPATH/vip-config to match production

[rinatkhaziev]

Description

For legacy reasons we were loading vip-config.php from /wp/wp-content/vip-config.php. This broke sunrise loader because it was expected to be loaded from ABSPATH . /vip-config/ rather than from WP_CONTENT_DIR . /vip-config/.

We've implemented a fallback loader in the dev env awhile back, so this change shouldn't negatively affect existing environments.

This also bumps DEV_ENVIRONMENT_VERSION to ensure that .lando.yml will be regenerated on startup.

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

1. Check out PR.
2. Run npm run build && npm link
3. Spin up an environment, add define( 'SUNRISE', true ); to wp-config-defaults.php
4. Make some changes to /vip-config/client-sunrise.php (like exit)or run a file_exists check fromwp shell`

[github-actions]

Dependency Review

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

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[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

[sjinks]

Looks good. My only concern is the pre-2023 environments (see Automattic/vip-container-images#516)