fix(cli): handle empty-value tag edits in interactive tag prompt

[Phil-Browne]

Extracted from #535 (ESD-1648) as a standalone fix, orthogonal to the validator-parity work in that PR.

The interactive tag editor keyed removal on value == "" && tags[key] != "", which had two bugs:

• It refused to remove a tag whose current value was already empty.
• Entering an empty value for a key that did not exist silently dropped the key with no feedback.

Now key existence is checked explicitly: an empty value removes the tag if present, otherwise reports "nothing to remove". Fixed in both the native (prompts.go) and WASM (prompts_wasm.go) paths, which had drifted out of sync.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.58%. Comparing base (9ba6a3b) to head (842e4de).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #539      +/-   ##
==========================================
+ Coverage   78.57%   78.58%   +0.01%     
==========================================
  Files         192      192              
  Lines       18522    18525       +3     
==========================================
+ Hits        14553    14558       +5     
+ Misses       2904     2902       -2     
  Partials     1065     1065              

Files with missing lines	Coverage Δ
internal/utils/prompts.go	77.49% <100.00%> (+0.25%)	⬆️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

Fixes edge cases in the interactive tag editor so that entering an empty value removes an existing tag regardless of its current value (including already-empty values), and produces deterministic feedback when attempting to remove a non-existent key. The change is applied consistently across both native and WASM prompt implementations to prevent behavior drift.

Changes:

• Update tag-edit removal logic to check key existence explicitly (instead of tags[key] != "").
• Add regression tests for the native prompt behavior (empty-existing-value removal and no-op removal attempt).
• Add a WASM regression test for the “remove non-existent key” no-op case.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
internal/utils/prompts.go	Fix native interactive tag-removal semantics by checking key existence.
internal/utils/prompts_wasm.go	Mirror the native fix in the WASM prompt path to eliminate drift.
internal/utils/prompts_wasm_test.go	Add a regression test for the WASM “empty value for missing key” no-op behavior.
internal/utils/prompts_test.go	Add native regression tests for removing empty-valued tags and handling empty values for new keys.

[penzeliz-megaport]

Reviewed for correctness; no findings. LGTM.