Title: Unexpected Behavior: Verdaccio 5.5.0 Checking Uplink First Instead of Local Storage

[joh-zhang]

I deployed the Verdaccio 5.5.0 service using the Helm chart version 4.8.0. According to the official documentation, Verdaccio should look for npm packages locally first upon receiving a request, and only check the uplink if the package is not found locally. However, based on the following logs, it appears that Verdaccio is checking the uplink first upon receiving a request, and only looking locally if the package is not found in the uplink. This behavior seems inconsistent with the official documentation. Are there any special parameters that need to be configured?

http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.18.43.198 requested 'GET /test3-package'
 info --- auth/allow_action: access granted to: �[90mundefined�[39m
 info --- allowed access for test3-package
 info --- making request: 'GET https://registry.npmmirror.com/test3-package'
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- ERR, req: 'GET https://registry.npmmirror.com/test3-package', error: ETIMEDOUT
 http --- �[33m304�[39m, user: �[1mnull�[22m(172.18.43.198), req: 'GET /test3-package', bytes: �[33m0�[39m/�[33m0�[39m
 http --- 172.18.43.198 requested 'POST /-/npm/v1/security/audits/quick'
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.18.43.198), req: 'POST /-/npm/v1/security/audits/quick', bytes: �[33m916�[39m/�[33m0�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m
 http --- 172.16.0.198 requested 'GET /-/ping'
 http --- �[33m200�[39m, user: �[1mnull�[22m(172.16.0.198), req: 'GET /-/ping', bytes: �[33m0�[39m/�[33m3�[39m