Fix/kubernetes devcontainer template to require fewer updates on initial deployment

[greg-the-coder]

Description

Identified changes to template so that it can be used "out of the box" with fewer updates across a wider variety of coder deployments. Tested on base AWS EKS cluster that used AWS Linux/Bottlerocket node group.

Type of Change

• New module
• Bug fix
• Feature/enhancement
• Documentation
• Other

Testing & Validation

• Tests pass (bun test)
• Code formatted (bun run fmt)
• [X ] Changes tested locally

Related Issues

None

[DevelopmentCats]

Suggested change

	# Note: May not work on AWS Linux Nodes
	# metadata {
	# display_name = "CPU Usage"
	# key = "0_cpu_usage"
	# script = "coder stat cpu"
	# interval = 10
	# timeout = 1
	# }
	# Note: May not work on AWS Linux Nodes
	# metadata {
	# display_name = "RAM Usage"
	# key = "1_ram_usage"
	# script = "coder stat mem"
	# interval = 10
	# timeout = 1
	# }
	# Note: May not work on AWS Linux Nodes
	metadata {
	display_name = "CPU Usage"
	key = "0_cpu_usage"
	script = "coder stat cpu"
	interval = 10
	timeout = 1
	}
	# Note: May not work on AWS Linux Nodes
	metadata {
	display_name = "RAM Usage"
	key = "1_ram_usage"
	script = "coder stat mem"
	interval = 10
	timeout = 1
	}

@greg-the-coder Would it maybe be worth just adding the Note and leaving the stats. Since not all people would be using kubernetes with aws?

[greg-the-coder]

70%+ of our enterprise, paying customers run Coder on AWS. Also, I ran into the same issue when working with the SUSE/Rancher folks earlier in the year when I was helping them prep a Devcontainer demo for SUSECON. I would prefer to leave that commented out, and then someone could uncomment it if they wanted it, so it at least works out of the box. What I'm seeing in the field on a couple of the customer POVs I've shadowed is the reverse, where we have to walk customers through "tweaking" the templates before they work, which isn't ideal.