Upgrade Jinja2 dependency version specification to address CVE-2024-22195

[QMalcolm]

resolves CVE-2024-22195

Problem

CVE-2024-22195 identified an issue in Jinja2 versions <= 3.1.2.

Solution

We've gone changed our dependency requirement specification to be 3.1.3 or greater (but less than 4).

Note: Preivously we were using the ~= version specifier. However due to some issues with the ~= we've moved to using >= in combination with <. This gives us the same range that ~= gave us, but avoids a pip resolution issue when multiple packages in an environment use ~= for the same dependency.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
• This PR includes type annotations for new and modified functions

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.00%. Comparing base (869ba18) to head (07635ec).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9638   +/-   ##
=======================================
  Coverage   88.00%   88.00%           
=======================================
  Files         176      176           
  Lines       22311    22311           
=======================================
  Hits        19634    19634           
  Misses       2677     2677           

Flag	Coverage Δ
integration	85.59% <ø> (ø)
unit	62.09% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[github-actions]

The backport to 1.6.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-9638-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7ea46708327260c85460d8034ef6ab84fe3d1b78
# Push it to GitHub
git push --set-upstream origin backport-9638-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest

Then, create a pull request where the base branch is 1.6.latest and the compare/head branch is backport-9638-to-1.6.latest.

[github-actions]

The backport to 1.5.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.5.latest 1.5.latest
# Navigate to the new working tree
cd .worktrees/backport-1.5.latest
# Create a new branch
git switch --create backport-9638-to-1.5.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7ea46708327260c85460d8034ef6ab84fe3d1b78
# Push it to GitHub
git push --set-upstream origin backport-9638-to-1.5.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.5.latest

Then, create a pull request where the base branch is 1.5.latest and the compare/head branch is backport-9638-to-1.5.latest.