Bicep Snapshots and What-if degredation with latest version and public Azure

**Bicep version**
Bicep CLI version 0.39.26 (1e90b06e40)

**Describe the bug**
I have noticed that bicep snapshot and what-if degraded with latest release. I am mentioning what-if because I see the same issues I see in snapshot in what-if as well when doing actual deployment. To illustrate the problem I am providing a screenshot of Bicep snapshots compare command:

The screenshots shows compare to the same bicep parameters file and same bicep template but ran via latest bicep cli version. As you can see previously it was able to put the correct values by interpreting the conditions in the code and now it is not able to. It just puts the code. Below is also screenshot from the same what-if issues shown in actual deployment:

I know that bicep snapshots is in preview but what-if is not so that is serious degradation. Some of the conditions are more complex but some are quite simple like if than and event they do not work properly. Note also that depending on the input certain properties are shown with difference on one resource but on another one are not. @stephaniezyen I am mentioning you as I thing this is big issue that requires some attention.

**To Reproduce**
If needed I can provide the files offline to troubleshoot.

**Additional context**
Add any other context about the problem here.

Start by reproducing the behavior with Bicep CLI 0.39.26 using the same template and parameters file described in the issue. Compare snapshot output and deployment what-if results with the earlier behavior; the issue is done when conditional property values are interpreted consistently rather than displayed as code.

Written by the indexing model from the issue text.