digitalasset/canton image may cached settings for image and version

If you run the example and build the local images for digitalasset/canton, http-json or trigger-service, it may cache the settings in .env. If you later update .env to switch to Enterprise version (for example) then the image may not get rebuilt and you continue to use the original version of the package services.

Start by tracing how the local digitalasset/canton, http-json, and trigger-service images consume settings from .env and how image rebuild decisions are made. Reproduce the issue by changing the package version in .env after building an image, then verify that the subsequent run uses the updated version rather than cached settings.

Written by the indexing model from the issue text.