fix: clarify bootstrap message when using docker port mapping

[MuzzaiyyanHussain]

What

Clarifies the bootstrap startup messages to avoid misleading port information when running Infisical with Docker port mappings.

Why

When Infisical is run using Docker port mapping (for example -p 8080:3000 or behind a reverse proxy), the bootstrap message displays the container port (appCfg.PORT). This can confuse users because the externally accessible URL may differ, even though Infisical itself works correctly.

How

Added a clarification note to the bootstrap messages indicating that the exposed host port may differ when running in Docker, instead of assuming a specific external URL.

Testing

• Change is limited to log message clarification only
• No runtime or functional behavior was modified

fixes #5295

[maidul98]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds a clarification note to the bootstrap startup messages to help users understand that when running Infisical in Docker with port mapping, the externally accessible port may differ from the internal container port displayed in the message.

• Added portNote variable containing the clarification message
• Included the note in both initialization paths (new installation and returning user)
• Change is limited to user-facing console messages only - no functional code modified

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The change is limited to adding a user-facing clarification message to console output, with no modifications to functional code, logic, APIs, or database interactions
• No files require special attention

Important Files Changed

Filename	Overview
backend/src/server/boot-strap-check.ts	Added clarification note to bootstrap messages about Docker port mapping - no functional changes

[MuzzaiyyanHussain]

@maidul98

[MuzzaiyyanHussain]

@scott-ray-wilson