fix: permission verification per environment default when empty

[petruki]

This pull request primarily introduces a minor code enhancement in the permission helper to provide a default value for environment checks. The issue happens when a permission is applied explicitly for default (production) environment, though redundant, this is a valid permission but results in an invalid check because some resource accesses do not supply the environment and should always fallback to default.

How to simulate

1. Create a team permission for reading Switchers
2. Select default environment when creating
3. Save or enable

Expected result

Switcher is accessible for default environment only

Dependency Updates

• Upgraded core dependencies: express to 5.2.1, jsonwebtoken to 9.0.3, and pino-pretty to 13.1.3 for improved security and stability. [1] [2] [3] [4] [5]
• Updated several sub-dependencies including body-parser, finalhandler, iconv-lite, fast-copy, jwa, jws, and others, ensuring compatibility with the latest Node.js versions and upstream bug fixes. [1] [2] [3] [4] [5] [6]
• Refreshed browser compatibility packages: browserslist, caniuse-lite, electron-to-chromium, and update-browserslist-db for more accurate environment targeting. [1] [2] [3] [4] [5]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud