Add ReadMe troubleshooting section for network start issues

[mitnick2012]

Overview
When icp network start exits with status 101, the terminal output gives no
actionable information. The actual error (e.g. port conflict) is silently written
to a log file that new users have no reason to know exists. This leaves developers
stuck with a cryptic error and no clear path to resolution.

Requirements

• Document where to find the real error log
• Cover the most common root cause (port 8000 already in use)
• Provide a concrete fix for the Docker port conflict case
• The fix must get icp network start -d running successfully

Considered Solutions

1. Improve the CLI output to surface the log file contents directly in the terminal
   instead of just reporting exit status 101 — this would be the ideal long-term fix
   but requires changes to the network launcher itself.
2. Document the issue in the troubleshooting guide so users can self-diagnose
   immediately — low effort, high impact, no code changes required.

Recommended Solution
Option 2 — documentation. It unblocks users today without touching any code.
The log file path and the port conflict error message are stable and reliable
signals, making them safe to document. Option 1 is worth a separate issue/PR
targeting the CLI itself.

Considerations

• Security: None. No code changes, no new behavior.
• Performance: None.
• Users: Purely additive. Existing workflows are unaffected; new users get
  a faster path to resolution instead of hitting a dead end.
• Breaking changes: None.
• Maintenance: Low. The log file path and pocket-ic port binding behavior
  are unlikely to change frequently. If the default port ever changes, this
  section will need a one-line update.

[cla-idx-bot]

Dear @mitnick2012,

In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA.

If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged.

— The DFINITY Foundation

[marc0olo]

@mitnick2012 thanks for the contribution. I forwarded the issue to the team as I think it's better to fix the feedback in the icp-cli directly instead of documenting the problem across the board.

[mitnick2012]

Yes its better to fix in the cli,and I suggest to let the fix of the problem here

[marc0olo]

@mitnick2012 this should we solved in the latest icp-cli version: https://github.com/dfinity/icp-cli/releases/tag/v1.3.0

if you still experience this, please file an issue here