chore: bump version to 4.16.2 (hotfix - reclaim npm latest tag)

[TsuyoshiUshio]

Summary

Hotfix release to reclaim the latest npm tag from erroneously tagged 3.6.0.

Changes

• Bump version from 4.16.1 to 4.16.2 in package.json, src/constants.ts, package-lock.json
• Revert eslint from ^10.6.0 to ^8.57.0 to fix CI peer dependency conflict

eslint Downgrade Rationale

PR #456 upgraded eslint to ^10.6.0, but the plugin ecosystem was not updated:

• @typescript-eslint/eslint-plugin@^5.12.1 declares peerDependencies: { eslint: '^6.0.0 || ^7.0.0 || ^8.0.0' }
• @typescript-eslint/parser@^5.12.1 has the same constraint
• eslint-plugin-deprecation@^1.3.2 requires @typescript-eslint/parser@^5

This causes npm ci to fail with ERESOLVE in CI (strict peer dependency checking in npm v7+).

Alternatives Considered

Option	Pros	Cons
Upgrade @typescript-eslint to v8+	Full eslint 10 support	Requires flat config migration, breaks eslint-plugin-deprecation, large scope for a hotfix
Add .npmrc with legacy-peer-deps=true	Minimal change	Workaround, masks real incompatibility, not a proper fix
Revert eslint to ^8.57.0 (chosen)	Restores working CI, minimal risk, matches plugin ecosystem	eslint 8 is deprecated (EOL)

The chosen approach restores CI while keeping the change scope minimal for a hotfix. A proper eslint 10 migration (with flat config + @typescript-eslint v8 + replacement for eslint-plugin-deprecation) should be done in a dedicated PR.

Notes

• This is identical to v4.16.1 content-wise for the npm package, only the version number is changed
• npm package already published manually as @azure/functions@4.16.2 with latest tag
• The eslint fix applies only to the dev toolchain and does not affect the published package