[CDTOOL-1193] Support for Logging Endpoint Errors

[rcaril]

Change summary

This PR adds support for the service logging debug commands, which streams logging endpoint errors.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

• Does your submission pass tests?

 make test TEST_ARGS="-run TestParseLoggingError  ./pkg/commands/service/logging/debug"
ok      github.com/fastly/cli/pkg/commands/service/logging/debug        1.017s

Changes to Core Features:

• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?

Example Output:

INFO: Streaming logging endpoint errors for service <SID>

14:55:10 | Broken Log | Get "https://my-broken.logging.org/.well-known/fastly/logging/challenge": lookup my-broken.logging.org. on 127.0.0.1:53: no such host
14:55:21 | Broken Log | Get "https://my-broken.logging.org/.well-known/fastly/logging/challenge": lookup my-broken.logging.org. on 127.0.0.1:53: no such host
14:55:24 | Broken Log | Get "https://my-broken.logging.org/.well-known/fastly/logging/challenge": lookup my-broken.logging.org. on 127.0.0.1:53: no such host

---

Note: Claude Code was leveraged to build this feature

[kpfleming]

This is fine as-is, but I've suggested some minor improvements.

[kpfleming]

This is really minor, but since there aren't any subcommands all references to RootCommand should be DebugCommand.

[rcaril]

Moved in 114dbcd.

[rcaril]

It looks like the linter is throwing an error now due to the naming convention:

pkg/commands/service/logging/debug/root.go:28:6: exported: type name will be used as debug.DebugCommand by other packages, and that stutters; consider calling this Command (revive)
type DebugCommand struct {

Thoughts @kpfleming - should we revert it back or see if a override can be used?

[rcaril]

Added an override in f09a9c3 for the time being.

[kpfleming]

It's actually fine to just call it Command too, since it is the only command in this package.

[rcaril]

Maybe we'll ask @anthony-gomez-fastly to make the deciding call on this one :)