Standardize `containerEnv` and edits to the $PATH variable

As seen in a recent PR (https://github.com/devcontainers/features/pull/153), the current pattern for editing important variables like `$PATH` are highly dependent on the technique the author chose to employ (editing `*rc` files, `containerEnv` properties), as well as the _order_ in which both features and the declared variables are listed.

For consistency I believe we need to find a pattern (or perhaps invent some new attribute/concept in the `devcontainer-feature.json`) that allows us to safely and consistently apply container variables in a reproducible way.

## The issue

> Copied from https://github.com/devcontainers/features/pull/153#discussion_r970164559

I think this pattern that we've adopted here (using one containerEnv inside another) -_might_ be dangerous moving forward, since I think that the order this object is emitted into the intermediate Dockerfile is important. Right now the tooling ends up emitting in the provided order

Notably, this output is different when using docker exec directly

Changing the order to:

```
"containerEnv": {
"PATH": "${PATH}:${CONDA_DIR}/bin",
"CONDA_SCRIPT":"${CONDA_DIR}/etc/profile.d/conda.sh",
"CONDA_DIR": "/opt/conda"
}
```

The auto-generated test fails:

cc @jungaretti @devcontainers/maintainers

issue に記載されている devcontainer-feature.json の containerEnv パターンから始め、中間的な Dockerfile 出力と docker exec の動作を比較します。変数の順序が変わると失敗する自動生成テストを確認します。feature や宣言の順序に依存せず、PATH などの変数を適用する再現可能なパターンを定義できれば完了です。

索引モデルが issue の本文から書いたものです。