Existing walkthrough cleanup

[Racer159]

Describe what should be investigated or refactored

We need to cleanup our existing walkthroughs on docs.zarf.dev to match the new style of walkthrough bein introduced via the Big Bang component and the OCI publish PRs

Links to any relevant code

https://github.com/defenseunicorns/zarf/tree/main/docs/13-walkthroughs
https://github.com/defenseunicorns/zarf/blob/bigbang-component/docs/13-walkthroughs/5-big-bang.md

Walkthroughs to be updated

• Using Zarf Package Create - @laurenmengert
• Combine Initializing a K8s Cluster and Initializing a New K8s Cluster - @josiblair
• Deploying Packages - @JasonvanBrackel
• Add Logging - @JasonvanBrackel

Additional context

Our existing PRs are confusing and do not match the tone or style that we wish of the Zarf project. This should be fixed so that people have an excellent introduction to using Zarf and these can be used more to help people learn about and use Zarf

[Racer159]

Link: https://docs.zarf.dev/docs/walkthroughs/

[Racer159]

Something that would be really nice to do where we are showing Zarf console output in walkthroughs would be to use a tool like ansi2html (https://github.com/kilobyte/colorized-logs) to capture it. This would render as text the same size as the instructions and would be copy/pasteable and should still have colors in our docs site.

- name: GIT_SERVER_CPU_REQ
  description: The CPU request for git server
  default: 200m
- name: GIT_SERVER_MEM_REQ
  description: The memory request for git server
  default: 512Mi
- name: GIT_SERVER_CPU_LIMIT
  description: The CPU limit for git server
  default: "3"
- name: GIT_SERVER_MEM_LIMIT
  description: The memory limit for git server
  default: 2Gi
constants:
- name: AGENT_IMAGE
  value: agent:local
This package has 9 artifacts with software bill-of-materials (SBOM) included. You can view them now
in the zarf-sbom folder in this directory or to go directly to one, open this in your browser:
/home/wayne/workspace/zarf/zarf-sbom/sbom-viewer-docker.io_grafana_promtail_2.7.0.html

* This directory will be removed after package deployment.

?  Deploy this Zarf package? (y/N) 

Not a requirement for this issue, but something that would add a bit to the docs as people go through them. It would also be editable so that if one small part of verbiage updated you wouldn't need to run through a whole walkthrough just to get to that section to retake a good screenshot.

[JasonvanBrackel]

@Racer159 ☝️