chore: Use shared source structures for aws firehose

[kalleep]

Pull Request Details

1. Use loki.Fanout and source.Consume
2. Remove grpc block, dskit will always start a grpc server along side http but there is no way for aws to call this server.
3. Don't use component id in metric names, dskit server exposes some metrics that we currently don't document but these should not be prefixed with component id but with component name like we do in loki.source.api. This is fine because all metircs have component_id as label and these are not documented.

There is other fixes I want to do too this component but will do that in a follow up.

Issue(s) fixed by this Pull Request

Notes to the Reviewer

PR Checklist

• Documentation added
• Tests updated
• Config converters updated

BREAKING-CHANGE: Renamed undocumented metrics that was previously prefixed with <component_id><metric_name> to loki_source_awsfirehose<metric_name>

[github-actions]

💻 Deploy preview available (chore: use shared source structures for aws firehose ):

• https://deploy-preview-alloy-5739-zb444pucvq-vp.a.run.app/docs/alloy/latest/

[clayton-cornell]

Makes sense form a docs standpoint. Data Firehose only sends HTTP requests.

[kalleep]

@ptodev Created a issue about documenting these metrics #5751

[kalleep]

It's a bit weird that we cannot prevent the grpc server from starting. Currently these components do not pass a port for it so a port will be selected at random. But this also means a random port will be occupied and while it's unlikely it could collide with another configured port.

[github-actions]

💻 Deploy preview deleted (chore: Use shared source structures for aws firehose ).