feat: add support for templated components

[kentquirk]

Which problem is this PR solving?

• Adds support for components that are defined in a data file and use a Go template to generate config information.

Short description of the changes

• Create a couple of templated components
• Create the infrastructure that can load and render them
• Integrate into HPFS as a component type
• Extend the generation functions to accept a map of userdata
• Create a slimmer hpsf demo file (hpsf2)

[codeboten]

Suggested change

	default: ${HONEYCOMB_TRACES_APIKEY}
	default: ${HONEYCOMB_API_KEY}

[kentquirk]

This was deliberate to avoid confusion with API keys you may be using for other purposes; it's not a world where one honeycomb key makes sense anymore. I think it's likely that you'll have multiple Honeycomb keys, so I've changed the name to make it even clearer.

[codeboten]

Suggested change

	summary: Export traces to Honeycomb in Honeycomb's event format
	summary: Export telemetry to Honeycomb

[codeboten]

my suggestion here is that this component could be generic enough to emit any kind of data to honeycomb, the export format might not be necessary to call out in the documentation of the component.

[kentquirk]

This component today only applies to Refinery, but it's a good point that logs can also flow through Refinery. So I changed it to telemetry but left in the "event format" part.