Add low aspect ratio demo case to the tracker

[clmould]

Description

Closes #3554

Checklist

I confirm that I have completed the following checks:

• My changes follow the PROCESS style guide
• I have justified any large differences in the regression tests caused by this pull request in the comments.
• I have added new tests where appropriate for the changes I have made.
• If I have had to change any existing unit or integration tests, I have justified this change in the pull request comments.
• If I have made documentation changes, I have checked they render correctly.
• I have added documentation for my change, if appropriate.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 42.74%. Comparing base (25480ae) to head (4698b7f).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4020      +/-   ##
==========================================
- Coverage   45.89%   42.74%   -3.16%     
==========================================
  Files         123      123              
  Lines       29064    32648    +3584     
==========================================
+ Hits        13340    13954     +614     
- Misses      15724    18694    +2970     

☔ 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.

[timothy-nunn]

Just need to check that @ajpearcey is happy with this file:
low_aspect_ratio_DEMO.MFILE.DAT.txt
low_aspect_ratio_DEMO.MFILE.DATSUMMARY.pdf
low_aspect_ratio_DEMO.OUT.DAT.txt

[ajpearcey]

The burn time in this file drops from 2.11 hours to 1.4 hours. I will investigate why, I'm not comfortable adding this to the tracker until we understand this change.

[timothy-nunn]

The burn time in this file drops from 2.11 hours to 1.4 hours. I will investigate why, I'm not comfortable adding this to the tracker until we understand this change.

👍. Is there a constraint we can use to get the burn time back up? Or is already a constraint that is being violated.