Point gpui dependencies at gpui-kit and randomize screenshot-safe display data - #241

Description

Two maintenance changes on top of main.

1. Follow the upstream rename to gpui-kit

longbridge/gpui-component has been renamed to longbridge/gpui-kit, and the fork to feigeCode/gpui-kit. Every gpui-* dependency URL, the [patch] entry, the docs page and the two sync scripts now point at the new repository. While updating them, three matchers in script/update_gpui_component_revision.py that were still pinned to the old repository name were fixed:

• The guard required the literal gpui-component.git, which never appears in the manifest — the check was dead code. It now matches the repository slug.
• lock_matches() only matched .git?rev=, but Cargo.lock sources have no .git, so the regex is now (?:\.git)?.
• Dependency lines that pin only rev and have no version raised cannot update dependency line for gpui-component. version is now optional.

Side effect: --update-navop now actually rewrites the five rev lines it was supposed to rewrite before.

2. Make screenshot-safe emit plausible, non-identifying data

The feature used to render one fixed placeholder per connection type, so every card looked the same and a screenshot showed nothing realistic. Display data is now derived deterministically from the connection ID:

• The same connection renders identically on every frame, while two different connections never share a name.
• Hosts are limited to example.com and the documentation ranges 192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24, so a screenshot can never point at a real host.
• Names mix English and Chinese technical styles (prod-mysql-07, stage-bastion-03, 订单系统-12).

Only display strings are replaced. HomePage.connections and HomePage.workspaces are left untouched, so encrypted storage, cloud sync and the actual connections keep using real data. app1.png is refreshed with a capture taken from a --features screenshot-safe build.

Screenshot

Captured with cargo run -p main --features screenshot-safe:

How to Test

cargo check --tests                                  # default features
cargo check --tests --features screenshot-safe
cargo test -p main --features screenshot-safe --bin navop -- screenshot_safe
python3 script/tests/test_update_gpui_component_revision.py
cargo metadata --locked

Expected: the two cargo check runs pass, screenshot_safe reports 6 passed, the revision script reports 4 passed, and cargo metadata --locked resolves the new repository URL.

Then run cargo run -p main --features screenshot-safe and confirm the home cards and the connection tree only show example.com or documentation-range hosts, with no repeated placeholder.

Checklist

• I have read the CONTRIBUTING document and followed the guidelines.
• Reviewed the changes in this PR and confirmed AI generated code (If any) is accurate.
• Passed cargo run for story tests related to the changes.
• Tested macOS, Windows and Linux platforms performance (if the change is platform-specific)

Only macOS was exercised; nothing here is platform-specific.