DOCS-1827: Update Go module logging examples

[andf-viam]

Update Golang logging example code for module creation docs

• Including new example for CWarnw

[viambot]

Overall readability score: 55.57 (🟢 +0)

File	Readability
_index.md	51.88 (🟢 +0)

View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File	Readability	FRE	GF	ARI	CLI	DCRS
_index.md	51.88	37.44	11.65	16.3	12.48	6.14
	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0

Averages:

	Readability	FRE	GF	ARI	CLI	DCRS
Average	55.57	47.43	10.64	13.22	12.09	7.61
	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0

View metric targets

Metric	Range	Ideal score
Flesch Reading Ease	100 (very easy read) to 0 (extremely difficult read)	60
Gunning Fog	6 (very easy read) to 17 (extremely difficult read)	8 or less
Auto. Read. Index	6 (very easy read) to 14 (extremely difficult read)	8 or less
Coleman Liau Index	6 (very easy read) to 17 (extremely difficult read)	8 or less
Dale-Chall Readability	4.9 (very easy read) to 9.9 (extremely difficult read)	6.9 or less

[benjirewis]

Nice! Just some nits on CInfo vs CInfof vs CInfow.

[viambot]

You can view a rendered version of the docs from this PR at https://docs-test.viam.dev/2632

[npentrel]

Is there a reason why these methods are named with a C at the beginning? It feels rather unintuitive

[benjirewis]

It was a decision the NetCode team made a while ago. Most loggers have methods that look like Debug, Debugf, and Debugw for all log levels. Most loggers also do not take a context.Context. We wanted to take a context on our logging methods to pass some "extra" information along with each log that could help with debugging the path a single operation was taking through the RDK. When an alternative version of a method that is otherwise identical to the original but offers a context.Context param is written in Golang, it's common practice to name that method either FooCtx of CFoo. We went with the latter.