fix(deps): update dependency mitol-django-hubspot-api to v2025

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
mitol-django-hubspot-api	==2023.12.19 → ==2025.12.18

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 mitol-django-hubspot-api
Using CPython 3.13.12
  × No solution found when resolving dependencies:
  ╰─▶ Because mitol-django-hubspot-api==2025.12.18 depends
      on hubspot-api-client==12.0.0 and your project depends
      on hubspot-api-client>=6.1.0,<7, we can conclude that
      mitol-django-hubspot-api==2025.12.18 and your project are incompatible.
      And because your project depends on
      mitol-django-hubspot-api==2025.12.18, we can conclude that your
      project's requirements are unsatisfiable.

[asajjad2]

Blocking this based on https://github.com/mitodl/hq/issues/8295#issuecomment-3265357171

[sentry]

Bug: The mitol-django-hubspot-api dependency is being upgraded by two years, which introduces a risk of undocumented breaking changes that existing tests will not catch.
_{Severity: MEDIUM}

Suggested Fix

Before merging, review the changelog or release notes for mitol-django-hubspot-api between versions 2023.12.19 and 2025.12.18 to identify any breaking changes. If no changelog is available, perform integration testing in a staging environment to validate the Hubspot integration against the new library version.

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#L44

Potential issue: The `mitol-django-hubspot-api` dependency is being updated from version
`2023.12.19` to `2025.12.18`. This significant two-year version jump introduces a risk
of undocumented breaking changes. The application's test suite mocks the external API,
so it cannot detect if the real library API has changed. This could lead to runtime
failures in functions that interact with the Hubspot API, such as
`upsert_object_request` or `find_contact`, if their signatures or behavior have been
altered in the new version.

[sentry]

Bug: The pyproject.toml dependency version for mitol-django-hubspot-api does not match the version specified in the uv.lock file, which has not been updated.
_{Severity: HIGH}

Suggested Fix

Regenerate the uv.lock file to align it with the dependency versions specified in pyproject.toml. This will ensure that the build environment installs the correct dependency version (2025.12.18).

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#L43

Potential issue: The `pyproject.toml` file specifies version `2025.12.18` for the
`mitol-django-hubspot-api` dependency, but the `uv.lock` file has not been regenerated
and still pins the version to `2023.12.19`. This inconsistency will cause the CI/CD
pipeline to fail during dependency installation or will result in the old version of the
library being installed, defeating the purpose of the upgrade. The build process will
either fail or use an incorrect, older version of the dependency, preventing the
intended update from being deployed.

[sentry]

Bug: The pyproject.toml dependency mitol-django-hubspot-api was updated, but the uv.lock file was not regenerated. This will cause the CI build to fail.
_{Severity: HIGH}

Suggested Fix

Regenerate the uv.lock file to reflect the updated dependency version for mitol-django-hubspot-api specified in pyproject.toml. This will ensure the lockfile is consistent with the project's direct dependencies.

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#L43

Potential issue: The version for `mitol-django-hubspot-api` was updated to `2025.12.18`
in `pyproject.toml`, but the `uv.lock` file still contains the old version,
`2023.12.19`. The CI workflow runs `uv sync --locked`, which enforces that the lockfile
is consistent with `pyproject.toml`. Due to this mismatch, the command will fail,
blocking the CI pipeline and preventing the PR from being merged or deployed.