updating smart code snippet to not cause opacity 0 in hide element style

[segment-anthony]

There was a bug in VWO that was fix in legacy repository to which caused a 'flashing' issue. This was caused by the hide element style where opacity 0 was causing a quick 'flash' in the website.

Testing

• Added unit tests for new functionality
• Tested end-to-end using the local server
• [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
• [Segmenters] Tested in the staging environment
• [Segmenters] [If applicable for this change] Tested for regression with Hadron.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 33.14%. Comparing base (fdcc03e) to head (aa5b6dd).

❗ There is a different number of reports uploaded between BASE (fdcc03e) and HEAD (aa5b6dd). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (fdcc03e)	HEAD (aa5b6dd)
	2	1

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2686       +/-   ##
===========================================
- Coverage   78.52%   33.14%   -45.39%     
===========================================
  Files        1033       14     -1019     
  Lines       18702      694    -18008     
  Branches     3548      115     -3433     
===========================================
- Hits        14686      230    -14456     
+ Misses       2824      464     -2360     
+ Partials     1192        0     -1192     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[joe-ayoub-segment]

hi @segment-anthony thanks for raising this.
Is there any way you can test that this works before I deploy it on Monday?
With a PR like this I can't review the code in a meaningful way (I won't understand what the change it), so to reduce risk it's best to have some testing done. Would this be possible?

[joe-ayoub-segment]

Regarding testing. cc @segment-anthony
@seg-leonelsanches indicated that he tested this PR: #2654
which is identical this current new PR, apart from a css single line.

Screen.Recording.2025-01-17.at.15.11.24.mov