[docs] Improve pipeline section docs

[PadreSVK]

based on information provided:

• https://docs.google.com/document/d/1NeheFG7DmcUYo_h2vLtNRlia9x5wOJMlV4QKEK05FhQ/edit?tab=t.0#heading=h.g6rvvz3l271i
• https://github.com/open-o11y/opentelemetry-collector-testing/blob/master/docs/design.md#receivers

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: PadreSVK / name: Patrik Švikruha (ec7c3d1)

[mx-psi]

Thank you! Left one comment, I am not a technical writer so it may be that others have a better suggestion here

[svrnm]

Beyond the suggested change from @mx-psi this looks good to me. If you can fix that, we can merge it in

[chalin]

Suggested change

	As with components, use the `type[/name]` syntax to create additional pipelines for a given type.
	As with components, use the `type[/name]` syntax to create additional pipelines for a given type. Here is an example extending the previous configuration:

[chalin]

How about this so that we can keep the focus on what was added?

Suggested change

	```yaml
	service:
	pipelines:
	metrics:
	receivers: [opencensus, prometheus]
	processors: [batch]
	exporters: [opencensus, prometheus]
	traces:
	receivers: [opencensus, jaeger]
	processors: [batch, memory_limiter]
	exporters: [opencensus, zipkin]
	traces/better_pipeline:
	receivers: [opencensus]
	processors: [batch]
	exporters: [zipkin]
	```
	```yaml
	service:
	pipelines:
	# ...
	traces:
	# ...
	traces/better_pipeline:
	receivers: [opencensus]
	processors: [batch]
	exporters: [zipkin]
	```

[chalin]

Also, is there an alternative name to /better_pipeline that we can use? Previous examples in the page use /2.

[tiffany76]

Hi @PadreSVK, please take a look at the most recent suggested changes so we can move this PR forward. Thanks!