Cleanup: Extend CLI error wrapping to subscribe and config commands

[cubaseuser123]

This continues my error wrapping work from #3773. I checked the remaining CLI commands and found subscribe and the config subcommands still bypass the error wrapping layer in cmd/errors.go when run in an uninitialized directory. subscribe relied on a hardcoded inline fmt.Errorf. config ignored load errors.

This PR standardizes CLI error wrapping across the codebase.

It covers:

• Replacing the inline fmt.Errorf in subscribe with NewErrNotInitializedFromPath
• Wiring wrapConfigError in initConfigCommand so config subcommands (labels, envs, volumes, git) get the standard help text
• Adding "subscribe" and "config" cases to the ErrNotInitialized.Error() switch

(Side note: I added cmd/errors_test.go. In the previous PR, we hit a Codecov block because we missed testing the wrapper functions directly, leaving patch coverage around 40%. This time, I added tests for wrapSubscribeError, wrapConfigError, and the other wrappers to guarantee 100% patch coverage.)

all other tests pass locally, let me know if any further changes are required!

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cubaseuser123
Once this PR has been reviewed and has the lgtm label, please assign dsimansk for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[knative-prow]

Hi @cubaseuser123. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

❌ Patch coverage is 66.21622% with 50 lines in your changes missing coverage. Please review.
✅ Project coverage is 54.05%. Comparing base (a6ba689) to head (9f3c2aa).

Files with missing lines	Patch %	Lines
cmd/errors.go	66.20%	46 Missing and 3 partials ⚠️
cmd/config.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3837      +/-   ##
==========================================
+ Coverage   54.03%   54.05%   +0.02%     
==========================================
  Files         200      200              
  Lines       23567    23709     +142     
==========================================
+ Hits        12734    12817      +83     
- Misses       9604     9664      +60     
+ Partials     1229     1228       -1     

Flag	Coverage Δ
e2e	33.28% <2.70%> (-0.21%)	⬇️
e2e go	29.22% <0.00%> (-0.20%)	⬇️
e2e node	25.56% <0.00%> (-0.17%)	⬇️
e2e python	29.55% <0.00%> (-0.20%)	⬇️
e2e quarkus	25.68% <0.00%> (-0.18%)	⬇️
e2e rust	25.16% <0.00%> (-0.15%)	⬇️
e2e springboot	23.85% <0.00%> (-0.16%)	⬇️
e2e typescript	25.67% <0.00%> (-0.18%)	⬇️
e2e-config-ci	?
integration	15.62% <0.00%> (-0.11%)	⬇️
unit macos-14	43.08% <66.94%> (+0.16%)	⬆️
unit macos-latest	43.08% <66.94%> (+0.16%)	⬆️
unit ubuntu-24.04-arm	43.39% <66.21%> (+0.15%)	⬆️
unit ubuntu-latest	43.94% <66.94%> (+0.15%)	⬆️
unit windows-latest	43.15% <66.94%> (+0.16%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 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.