fix(deps): update dependency beautifulsoup4 to v4.14.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
beautifulsoup4 (changelog)	==4.8.2 → ==4.14.3

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package beautifulsoup4
Using CPython 3.13.12
  × No solution found when resolving dependencies:
  ╰─▶ Because wagtail==5.2.8 depends on beautifulsoup4>=4.8,<4.12 and your
      project depends on beautifulsoup4==4.14.3, we can conclude that your
      project and wagtail==5.2.8 are incompatible.
      And because your project depends on wagtail==5.2.8, we can conclude that
      your project's requirements are unsatisfiable.

[arslanashraf7]

This is blocked on Wagtail upgrade as per #3510 (comment).

[sentry]

Bug: The pyproject.toml dependency for beautifulsoup4 was updated, but the uv.lock file was not regenerated. This will cause the production build to fail.
_{Severity: CRITICAL}

Suggested Fix

Regenerate the uv.lock file to reflect the updated dependency version specified in pyproject.toml. This can be done by running the appropriate uv command to update and sync the lock file.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: pyproject.toml#L17

Potential issue: The `pyproject.toml` file specifies `beautifulsoup4==4.14.3`, but the
`uv.lock` file still contains version `4.8.2`. The production Docker build uses the `uv
sync --frozen` command, which enforces that the lock file's contents must match the
project's dependencies. This version mismatch will cause a constraint failure, leading
to a failed build in the CI/CD pipeline and preventing the application from being
deployed.

_{Did we get this right? 👍 / 👎 to inform future reviews.}