Fix: CI Javascript Lint Test

[CaseyLabs]

Description

• Simplify JavaScript linting in CI by routing the workflow through make js-lint.
• Limit JSHint to the maintained frontend files so unrelated or vendored scripts do not block PRs.
• Move the linting runtime from Node 20 to Node 22 so the repo stays on a currently supported LTS line.

Why

• Keep CI strict on the frontend code this repo actively maintains, without failing unrelated changes because of sample or third-party assets.
• Keep local and GitHub Actions linting on a supported Node LTS baseline for future contributors.

Changes

• Update .github/workflows/lint.yml to run make js-lint and use Node 22.
• Scope make js-lint in the Makefile to the maintained webclient and admin JavaScript paths.
• Update the Docker-based lint command in the Makefile from node:20 to node:22.
• Adjust .jshintrc for the browser-oriented frontend code and suppress the warnings used by these maintained scripts.
• Add the required /* global */ declarations in the affected frontend files, including window-gametime.js and window-map.js, so the lint step passes without changing runtime behavior.

Validation

• make js-lint

[Volte6]

JS linting should also check scripts defined in the _datafiles folder and nested folders. That's actually the primary purpose of the js linting - to make sure the scripts won't break when they are dynamically loaded/executed.

[CaseyLabs]

Updated make js-lint to lint every *.js file under _datafiles recursively, including nested world/sample scripts. Verified with make js-lint.