SetupEnv function in install script never seems to be callable

We are investigating why we can't turn off auto-update on our self-hosted IRs in containers because when it auto-updates then if things restart in the app service it will pull the original version of the IR (which is essentially a downgrade). This has caused some challenges for our data team members as they notice this behavior.

We would like to control this through rolling out new image versions that match the stable IR updates the MSFT puts out, however it doesn't seem like in the build.ps1 script that the SetupEnv function has any way of being called. Is that intentional or is there a reason that isn't at least callable using a flag?

Start with build.ps1 and trace how SetupEnv is defined and whether the install flow invokes it. Check how build or container options are passed, then confirm the requested behavior is controllable through a flag and does not force an unintended auto-update or downgrade.

Written by the indexing model from the issue text.