docs(guide): When suggesting alt dev profile, link to related issue

[epage]

What does this PR try to resolve?

Having sections in the build performance chapter link out to their issues is helpful for:

• giving hope that things will improve
• providing a place for people to subscribe to for updates
• raise visibility for ensuring we get appropriaet feedback (e.g. on degrading the debugger experience)

Noticed this was missing while writing up about this new chapter on the blog post.

How to test and review this PR?

[rustbot]

r? @weihanglo

rustbot has assigned @weihanglo.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[weihanglo]

"Tests Windows x86_64 gnu nightly" stack overflow: rust-lang/rust#139070

https://github.com/rust-lang/cargo/actions/runs/19479373309/job/55747288407?pr=16275#step:15:4742

 ---- profile_trim_paths::custom_build_env_var_trim_paths stdout ----
running `D:\a\cargo\cargo\target\debug\cargo.exe build -Ztrim-paths`
running `D:\a\cargo\cargo\target\debug\cargo.exe build -Ztrim-paths`
running `D:\a\cargo\cargo\target\debug\cargo.exe build -Ztrim-paths`
running `D:\a\cargo\cargo\target\debug\cargo.exe build -Ztrim-paths`
running `D:\a\cargo\cargo\target\debug\cargo.exe build -Ztrim-paths`

thread 'profile_trim_paths::custom_build_env_var_trim_paths' (2472) panicked at tests\testsuite\profile_trim_paths.rs:768:14:

test failed running `D:\a\cargo\cargo\target\debug\cargo.exe build -Ztrim-paths`
error: process exited with code 101 (expected 0)
--- stdout

--- stderr
   Compiling foo v0.0.1 (D:\a\cargo\cargo\target\tmp\cit\t2830\foo)

thread 'main' (10124) has overflowed its stack
error: could not compile `foo` (lib)

Caused by:
  process didn't exit successfully: `rustc --crate-name foo --edition=2015 src\lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --check-cfg cfg(docsrs,test) --check-cfg "cfg(feature, values())" -C metadata=9dd8a03acaba44eb -C extra-filename=-60a15610e42c1955 --out-dir D:\a\cargo\cargo\target\tmp\cit\t2830\foo\target\debug\deps -L dependency=D:\a\cargo\cargo\target\tmp\cit\t2830\foo\target\debug\deps` (exit code: 0xc00000fd, STATUS_STACK_OVERFLOW)cit\t2830\foo\target\debug\deps` (exit code: 0xc00000fd, STATUS_STACK_OVERFLOW)