feat: render tables on stdout

[mkcp]

Description

This PR adjusts a hack from before, which made sure we still rendered tables even when message / pterm was disabled via feature flags.

Now, we render them to Stdout instead of rendering them on Stderr like diagnostic logs. There is a slightly insane hack here to retrieve the current writer from a new atomic package var, then reinitialize Pterm with os.Stdout, and finally initialize it back to the original value.

This hack should be addressed as soon as possible with output writers that can be defined and utilized locally and are threadsafe, at least a far as providing atomic stdout writes, if possible.

Related Issue

Finishes #3223
Relates to #2576

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	500147c
🔍 Latest deploy log	https://app.netlify.com/sites/zarf-docs/deploys/672e9f9c3d17d70008784e79

[codecov]

Codecov Report

Attention: Patch coverage is 21.05263% with 15 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/cmd/package.go	0.00%	5 Missing ⚠️
src/cmd/common/table.go	0.00%	4 Missing ⚠️
src/pkg/message/connect.go	0.00%	3 Missing ⚠️
src/pkg/utils/yaml.go	0.00%	3 Missing ⚠️

Files with missing lines	Coverage Δ
src/cmd/connect.go	0.00% <ø> (ø)
src/cmd/dev.go	0.00% <ø> (ø)
src/cmd/root.go	0.00% <ø> (ø)
src/pkg/message/message.go	14.01% <100.00%> (+2.24%)	⬆️
src/pkg/message/connect.go	0.00% <0.00%> (ø)
src/pkg/utils/yaml.go	0.00% <0.00%> (ø)
src/cmd/common/table.go	0.00% <0.00%> (ø)
src/cmd/package.go	0.00% <0.00%> (ø)

[mkcp]

Hold off on review or merge, I need to look over the failing e2e tests.