Change default plotly version used to display plots

[backmari]

Description of the changes

• Change the default Plotly.JS version from 2 to 3.
• Remove obsolete option to fetch JSON data from Live Data Server (see Remove obsolete JSON format support from Live Data Server live_data_server#57).
• Extract dynamic Plotly loading logic from the HTML template into a static JavaScript resource that is imported in the template.

Background: A CIS reported that a plot was showing up as empty. It had been created with plotly 6 (compatible with Plotly.JS 3.) but was missing the plotly version tag injected by plot_publisher. Since Mantid is using plotly 6 now, new plots are more likely to be compatible with Plotly.JS 3., which should also be backwards compatible with plots created using an older version.

Check all that apply:

• updated documentation
• Source added/refactored
• Added unit tests
• Added integration tests
• (If applicable) Verified that manual tests requiring the /SNS and /HFIR filesystems pass without fail

References:

• Links to IBM EWM items: Story 15056: [WebMon] Change the default plotly version to 6
• Links to related issues or pull requests:

⚠️ Manual test for the reviewer

(Instructions for testing here)

There is a manual test to verify that a plot created without a version tag is displayed using Plotly.JS 3.0.1.

1. First, ensure that the data resources (/SNS/VULCAN/shared/autoreduce/reduce_VULCAN.py) are updated:

make clean
make all
# ensure the images and containers are rebuilt, e.g. using:
docker system prune -f -a --volumes

2. Build the images and stand up the containers:

make localdev/up
# wait for all containers to start
pixi run systemtests  # this will add the VULCAN instrument to the database

3. Open http://localhost/dasmon and log in as InstrumentScientist.
4. Open http://localhost/report/vulcan/12345/.
5. Submit for reduction by clicking "reduction".
6. Verify that the reduction completes and the plot is displayed using Plotly.JS 3.0.1. (There should also be a console log about the plotly version tag missing.)

Check list for the reviewer

• best software practices
  • clearly named variables (better to be verbose in variable names)
  • code comments explaining the intent of code blocks
• All the tests are passing
• The documentation is up to date
• code comments added when explaining intent

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.69%. Comparing base (dd8bdf1) to head (1f62713).
⚠️ Report is 12 commits behind head on next.

Additional details and impacted files

@@            Coverage Diff             @@
##             next     #287      +/-   ##
==========================================
+ Coverage   82.67%   82.69%   +0.02%     
==========================================
  Files          60       60              
  Lines        4434     4393      -41     
==========================================
- Hits         3666     3633      -33     
+ Misses        768      760       -8     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[darshdinger]

Two hopefully simple comments to address. Otherwise, looks great!

[darshdinger]

Looks good!