#51654: build: restore CHROMIUM_BUILDTOOLS_PATH in devcontainer config
Description of Change
Follow-up to #51558 to fix the failing codespaces prebuilds. This is an edge case because we hand roll a config here, and build-tools is still including CHROMIUM_BUILDTOOLS_PATH in configs and just ignoring it if the conditions are met. The condition check can't work without CHROMIUM_BUILDTOOLS_PATH in the config IF there's also no sync'd checkout (to create .gclient).
We'll remove this from the hand rolled config in the future when build-tools drops the conditional check for upstream depot_tools support.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
Release Notes
Notes: none
Backports
No Backports Requested
This pull request doesn't have any backports requested or created for older release branches.
What are backports?
Backports are copies of changes made to the main branch that are applied to older release branches. They ensure that bug fixes and important changes are available in maintained older versions of Electron.
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron