15831: Resolve Dependabot vulnerability alert by updating Next dependency

[MuralidharanGSF4527]

Bug description

Dependabot flagged an outdated and vulnerable version of Next.js in package.json.
The existing version (14.2.3) contained security advisories and compatibility warnings. Updating was required to maintain dependency stability and remove security alerts.

Root cause

The project was using an older Next.js (14.2.3) version that Dependabot identified as vulnerable or outdated. This caused dependency mismatch risks, potential security exposure, and triggered automated alerts. The version was not aligned with the recommended patch level for the framework used.

Solution description

Updated Next.js to the latest compatible patch version 14.2.8 as recommended by Dependabot.
This resolves the security alert, ensures dependency consistency, and improves build/runtime stability for the React PDF Viewer examples.

Reason for not identifying earlier

• Guidelines not followed. If yes, provide which guideline is not followed.

• Guidelines not given. If yes, provide which/who need to address.
  Tag label update-guideline-coreteam or update-guideline-productteam.

• If any other reason, provide the details here.

Areas tested against this fix

Provide details about the areas or combinations that have been tested against this code changes.

• Tested against feature matrix. Feature matrix link

Is it a breaking issue?

• Yes, Tag breaking-issue.
• NO

If yes, provide the breaking commit details / MR here.

Action taken

What action did you take to avoid this in future?

Feature matrix document updated

• Yes
• NO
• NA

Automation details - Mark Is Automated field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.

• BUnit, share corresponding MR.
• E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in automation dashboard.

If the same issue is reproduced in ej2, what will you do?

• Resolved. Provide MR link.
• NO. Created task to track it. Share task link.
• NA

Is this common issue need to be addressed in the same component or on other components in our platform?

• Yes - Need to check in other components, tag needs-attention-coreteam
• No

Output screenshots

Before Fix:

After Fix:

Blazor Checklist

Confirm whether this feature is ensured in both Blazor Server and WASM

• NA
• Yes
• NO

Is there any new API or existing API name change?

• Yes. If yes, Provide API Review task link.
• NO

Is there any existing behavior change due to this code change?

• Yes. Add breaking-change label.
• NO

Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)

• Yes
• NO

Reviewer Checklist

• All provided information are reviewed and ensured.

[AnanthaGokulaRaman]

Fine.