Update jinja2 requirement from <=3.1.4,>=3.1 to >=3.1,<=3.1.5

[ggainey]

Updates the requirements on jinja2 to permit the latest version.

• Release notes
• Changelog
• Commits

---

updated-dependencies:

• dependency-name: jinja2 dependency-type: direct:production ...

[patchback]

Backport to 3.22: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply ede2a44 on top of patchback/backports/3.22/ede2a442c306dfa1219ac20268a32bc0a759c913/pr-6179

Backporting merged PR #6179 into 3.63

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulpcore.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.22/ede2a442c306dfa1219ac20268a32bc0a759c913/pr-6179 upstream/3.22

4. Now, cherry-pick PR Update jinja2 requirement from <=3.1.4,>=3.1 to >=3.1,<=3.1.5 #6179 contents into that branch:

   $ git cherry-pick -x ede2a442c306dfa1219ac20268a32bc0a759c913

   If it'll yell at you with something like fatal: Commit ede2a442c306dfa1219ac20268a32bc0a759c913 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x ede2a442c306dfa1219ac20268a32bc0a759c913

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Update jinja2 requirement from <=3.1.4,>=3.1 to >=3.1,<=3.1.5 #6179 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.22/ede2a442c306dfa1219ac20268a32bc0a759c913/pr-6179

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.39: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.39/ede2a442c306dfa1219ac20268a32bc0a759c913/pr-6179

Backported as #6180

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.49: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.49/ede2a442c306dfa1219ac20268a32bc0a759c913/pr-6179

Backported as #6181

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.