PhpStorm Dev Containers: shared .idea settings embed machine-specific paths

A team wants a repeatable PhpStorm development environment using Dev Containers, with inspections, code style, and run configurations traveling alongside the container definition.

Committing the .idea directory looks like the obvious way to share that configuration. However, project settings can embed absolute paths, interpreter locations, and user-specific state, which may break on other machines or create merge conflicts. Native Dev Containers support also depends on the installed PhpStorm build.

Should .idea be committed for a Dev Containers workflow, or should teams rely on per-user settings and Settings Sync? Which .idea subdirectories are safe to share without exposing machine-specific paths? What approach handles PhpStorm build differences when sharing container-based project configuration?