Task: Init vcpkg submodule in env provision for full environments

When env provision creates a full (C++) environment it should automatically run git submodule update --init vcpkg in the new worktree so that cmake --preset works without a manual step. Light environments do not include vcpkg and should not have the submodule initialized.

• compass env provision with --type full (or default) automatically initializes the vcpkg submodule in the new worktree
• compass env provision --type light does not touch the vcpkg submodule
• cmake --preset linux-clang-debug-make works immediately after provision without a manual git submodule update step

After git worktree add succeeds and before writing the skeleton .env, run:

git submodule update --init vcpkg

in the new worktree directory when env_type = "full"=. A non-zero return code prints a warning but does not abort provisioning (the user can retry the submodule init manually).

Root cause: Git worktrees share the object store and ref list of the parent repository but do not automatically initialize submodules — each worktree is an independent working tree and submodule init must be run per-worktree.

Discovered while manually configuring solid-dirac, brave-hopper, and merry-newton after provisioning from ores_dev_prime_origin. Each required a manual git submodule update --init vcpkg before cmake --preset would work.

Merged as PR #1292. Added `git submodule update –init vcpkg` call in `env_create.py` immediately after `git worktree add` for `env_type == "full"` environments. Light environments are skipped. A failed init prints a warning but does not abort provisioning.