fix: pin next.js to 16.1.7 to mitigate CVE risk (closes #103)

[Ojas2095]

Closes #103

Pins next and eslint-config-next to exact version 16.1.7 (no caret) to mitigate known CVEs.

• package.json: next ^16.1.1 -> 16.1.7
• package.json: eslint-config-next ^16.1.1 -> 16.1.7

This prevents npm/yarn from resolving to any CVE-affected patch/minor releases.

[github-actions]

⚠️ This PR contains unsigned commits. To get your PR merged, please sign those commits (git rebase --exec 'git commit -S --amend --no-edit -n' @{upstream}) and force push them to this branch (git push --force-with-lease).

If you're new to commit signing, there are different ways to set it up:

Sign commits with gpg

Follow the steps below to set up commit signing with gpg:

1. Generate a GPG key
2. Add the GPG key to your GitHub account
3. Configure git to use your GPG key for commit signing

Sign commits with ssh-agent

Follow the steps below to set up commit signing with ssh-agent:

1. Generate an SSH key and add it to ssh-agent
2. Add the SSH key to your GitHub account
3. Configure git to use your SSH key for commit signing

Sign commits with 1Password

You can also sign commits using 1Password, which lets you sign commits with biometrics without the signing key leaving the local 1Password process.

Learn how to use 1Password to sign your commits.

[gemini-code-assist]

Code Review

This pull request updates the versions of next and eslint-config-next in package.json. However, the specified version 16.1.7 does not exist on the npm registry. Feedback was provided to use version 15.1.7 for both packages to ensure compatibility with React 19 and successful dependency resolution.

[gemini-code-assist]

The version 16.1.7 for the next package does not exist on the public npm registry. The current latest stable version is 15.1.7. Although the previous version was listed as ^16.1.1, that version also does not exist. Using a non-existent version will cause installation and build failures. Given the project's use of React 19 (as seen in lines 26-27), Next.js 15 is the appropriate major version to use.

Suggested change

	"next": "16.1.7",
	"next": "15.1.7",

[gemini-code-assist]

The version 16.1.7 for eslint-config-next does not exist on the npm registry. This version should be updated to match the Next.js version (likely 15.1.7) to ensure compatibility and successful dependency resolution.

Suggested change

	"eslint-config-next": "16.1.7",
	"eslint-config-next": "15.1.7",

[0xskr33p]

Both suggestions above from gemini aren't valid.

1. Please, rebase and sign your commit;
2. Also you need to build TU on your own with update wxtm-bridge-frontend repo after your changes and attach screenshots or recording that everything fine;