Centralize build feature profiles in Cargo metadata

[VitalyAnkh]

Summary

Fixes #10979.

This centralizes the Cargo feature matrix in app/Cargo.toml so the bundle scripts and Nix package resolve named build profiles from the same metadata instead of keeping their own stale feature lists.

• add package.metadata.warp.build_feature_groups and package.metadata.warp.build_profiles
• teach flake.nix to read the Nix build profile from Cargo metadata
• update bundle/deploy/run scripts to resolve profile features through the shared helper
• add script/check_cargo_build_profiles to validate the declared profile matrix
• keep the review-sensitive matrix behavior intact: Windows local includes agent_mode_debug, while macOS preview stays off heap diagnostics

Validation

• script/check_cargo_build_profiles --profile windows.local.app
• script/check_cargo_build_profiles --profile macos.preview.app
• script/check_cargo_build_profiles --profile macos.preview.cli
• script/check_cargo_build_profiles --all
• cargo metadata --format-version 1 --no-deps --locked --no-default-features --features "$features" --manifest-path app/Cargo.toml for every declared profile
• nix eval .#warp-terminal-experimental.buildFeatures --json
• nix eval --impure --expr 'let app = builtins.fromTOML (builtins.readFile ./app/Cargo.toml); in app.package.metadata.warp.nix.build_profile' --raw
• nix build .#warp-terminal-experimental --no-link --print-out-paths
• bash -n script/cargo_bundle_features.sh script/check_cargo_build_profiles script/deploy_remote_server script/deploy_remote_server_to_test_vm script/linux/bundle script/macos/bundle script/run script/wasm/bundle
• git diff --check

[oz-for-oss]

@VitalyAnkh

This PR is not linked to an issue that is marked with ready-to-implement.

Issue-state enforcement details:

• Associated same-repo issues checked: Failed to install warp through nix flake #10979

• Required readiness label: ready-to-implement

Readiness check:

• Failed to install warp through nix flake #10979: missing ready-to-implement; readiness labels present: none

To continue, link this PR to a same-repo issue such as Closes #123 in the PR description, and make sure that issue has ready-to-implement.

Powered by Oz

[oz-for-oss]

@VitalyAnkh

This PR is not linked to an issue that is marked with ready-to-implement.

Issue-state enforcement details:

• Associated same-repo issues checked: #10979

• Required readiness label: ready-to-implement

Readiness check:

• #10979: missing ready-to-implement; readiness labels present: none

To continue, link this PR to a same-repo issue such as Closes #123 in the PR description, and make sure that issue has ready-to-implement.

Powered by Oz