update VPN product pages with extension related changes (fix #15983)

[wen-2018]

If this changeset needs to go into the FXC codebase, please add the WMO and FXC label.

One-line summary

This PR updates the VPN product pages with extension related changes

Significant changes and points to review

See GH issue for details

Issue / Bugzilla link

#15983

Testing

http://localhost:8000/en-US/products/vpn/
http://localhost:8000/en-US/products/vpn/features/
http://localhost:8000/en-US/products/vpn/download/

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.57%. Comparing base (87f9f94) to head (fd63197).
Report is 7 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #16006   +/-   ##
=======================================
  Coverage   79.57%   79.57%           
=======================================
  Files         160      160           
  Lines        8396     8396           
=======================================
  Hits         6681     6681           
  Misses       1715     1715           

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

[alexgibson]

I haven’t pulled this PR locally yet to take a look, but I notice there’s quite a lot of new strings here. Do we need to think about fallbacks for older translations at all? We generally try not to show a lot of mixed English copy in places, unless it’s unavoidable. Maybe that discussion has already been had, just calling it out in case.

[wen-2018]

Do we need to think about fallbacks for older translations at all?

@alexgibson The new strings are on three pages:

• the landing page
  The new strings on this page is corresponding to the new image update. I removed the old ones since they are describing a feature for the old image

• the feature page
  This new string are for a new feature section and the old section with old strings are removed from the page. Since the new section is also added at the top, GH comparison made it look at a lot more strings are changed. In reality, it is removing the last section and adding a new one at the top

• the download page
  This purely adding a new link with a new string

Please let me know your thoughts on if any of the old strings should be used for fallbacks, especially the ones on the landing page

[alexgibson]

Updates look good! I'm not sure the new link on the download page is quite working as expected depending on operating system. But other than that, just a few small suggestions.

[alexgibson]

Issue: (possibly blocking) I'm not 100% sure what the expected behavior is here, but when visiting on a Windows device, I don't seem to see this new link:

When visiting on macOS (and Windows is a secondary CTA), I can see it though:

[alexgibson]

Oh one other question: when is this all due to launch? Does any of it need to be behind a switch?