fix: In getLedgerDevice() error, mention CGO_ENABLED=1

[jefft0]

Resolves #2737

As required by the HID library, the executable must be built with CGO_ENABLED=1 in order to find the Ledger. We want to keep building without this flag by default so that the binary is deterministic. So we just inform the user.

• In the getLedgerDevice error wrapped message, add "Try building with CGO_ENABLED=1"
• In the 'gnokey' command line code which calls this, print the error with "%+w" to show the wrapped message

The error message looks like:

unable to create Ledger reference in keybase, --= Error =--
Data: LedgerHID device (idx 0) not found. Ledger LOCKED OR Other Program/Web Browser may have control of device.
Msg Traces:
    0  gno/tm2/pkg/crypto/ledger/ledger_secp256k1.go:187 - ledger nano S. Try building with CGO_ENABLED=1
--= /Error =--

This PR is a minimal solution as an alternative to putting CGO_ENABLED=1 in the gnokey Makefile.

[Gno2D2]

🛠 PR Checks Summary

🔴 Pending initial approval by a review team member, or review from tech-staff

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🔴 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: jefft0/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🔴 Requirement not satisfied
└── 🔴 If
    ├── 🔴 Condition
    │   └── 🔴 Or
    │       ├── 🔴 At least one of these user(s) reviewed the pull request: [jefft0 leohhhn n0izn0iz notJoon omarsy x1unix] (with state "APPROVED")
    │       ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🔴 Else
        └── 🔴 And
            ├── 🟢 This label is applied to pull request: review/triage-pending
            └── 🔴 On no pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[codecov]

Codecov Report

❌ Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
tm2/pkg/crypto/ledger/ledger_secp256k1.go	0.00%	4 Missing ⚠️
tm2/pkg/crypto/keys/client/add_ledger.go	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!