fix(security): upgrade Bouncy Castle 1.81 → 1.84 (CVE-2025-14813)

[abdulbasit-syed]

Similar to #35897 but it's still in com.dotcms.tika-25.07.10_lts_v12.jar

Upgrade contains no breaking changes: https://dist.apache.org/repos/dist/release/tika/3.3.1/CHANGES-3.3.1.txt

Can be verified by running ./mvnw -pl :com.dotcms.tika -am dependency:tree -Dincludes=org.bouncycastle

Before:
[INFO] --- dependency:3.6.0:tree (default-cli) @ com.dotcms.tika --- [INFO] com.dotcms.core.plugins:com.dotcms.tika:bundle:1.0.0-SNAPSHOT [INFO] - org.apache.tika:tika-parsers-standard-package:jar:3.2.2:runtime
[INFO] - org.apache.tika:tika-parser-crypto-module:jar:3.2.2:runtime
[INFO] +- org.bouncycastle:bcjmail-jdk18on:jar:1.81:runtime
[INFO] | - org.bouncycastle:bcpkix-jdk18on:jar:1.81.1:runtime
[INFO] | - org.bouncycastle:bcutil-jdk18on:jar:1.81.1:runtime
[INFO] - org.bouncycastle:bcprov-jdk18on:jar:1.81:runtime

After:
[INFO] --- dependency:3.6.0:tree (default-cli) @ com.dotcms.tika --- [INFO] com.dotcms.core.plugins:com.dotcms.tika:bundle:1.0.0-SNAPSHOT [INFO] - org.apache.tika:tika-parsers-standard-package:jar:3.3.1:runtime
[INFO] - org.apache.tika:tika-parser-crypto-module:jar:3.3.1:runtime
[INFO] +- org.bouncycastle:bcjmail-jdk18on:jar:1.84:runtime
[INFO] | - org.bouncycastle:bcpkix-jdk18on:jar:1.84:runtime
[INFO] | - org.bouncycastle:bcutil-jdk18on:jar:1.84:runtime
[INFO] - org.bouncycastle:bcprov-jdk18on:jar:1.84:runtime

Proposed Changes

• change 1
• change 2

Checklist

• Tests
• Translations
• Security Implications Contemplated (add notes if applicable)

Additional Info

** any additional useful context or info **

Screenshots

Original	Updated
** original screenshot **	** updated screenshot **

[github-actions]

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

• This PR fixes #123 or Fixes: #123

• This PR closes #123 or Closes: #123

• This PR resolves #123 or Resolves: #123

• Other supported keywords: fix, fixed, close, closed, resolve, resolved
  Option 2: Link via GitHub UI (Note: won't clear the failed check)

1. Go to the PR → Development section (right sidebar)

2. Click "Link issue" and select an existing issue

3. Push a new commit or re-run the workflow to clear the failed check
   Option 3: Use branch naming
   Create a new branch with one of these patterns:

• 123-feature-description (number at start)

• issue-123-feature-description (issue-number at start)

• feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow

[mergify]

⚠️ The sha of the head commit of this PR conflicts with #36115. Mergify cannot evaluate rules on this PR. Once #36115 is merged or closed, Mergify will resume processing this PR. ⚠️