Update builder README instructions to include required modules

[shelbyspees]

Description:

Per this Slack thread, the builder was recently updated not to include any components by default.

This PR updates the README's TL;DR example to explicitly include the required core collector modules (OTLP receiver, batch processor, and logging exporter). Without them, the collector you build following those instructions fails to run.

Link to tracking issue:

n/a (I just went ahead and opened this PR)

Testing:

To reproduce the failure:

• Clone open-telemetry/opentelemetry-collector at bed95f1
• Navigate into cmd/builder
• Follow TL;DR instructions, creating ~/.otelcol-builder.yaml that only includes alibabacloudlogserviceexporter and no other modules
• Build the collector
• Run the collector using the provided /tmp/otelcol.yaml in the instructions
• You should get the following error: unknown receivers type "otlp" for "otlp"

After rebuilding the collector with the updated ~/.otelcol-builder.yaml listing all the required modules, it will run successfully.

[codecov]

Codecov Report

Merging #4664 (adac549) into main (bed95f1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #4664   +/-   ##
=======================================
  Coverage   90.68%   90.68%           
=======================================
  Files         179      179           
  Lines       10618    10618           
=======================================
  Hits         9629     9629           
  Misses        767      767           
  Partials      222      222           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bed95f1...adac549. Read the comment docs.

[Aneurysm9]

Might also be good to update the fuller example under Configuration as that would build a collector with only an exporter.

[bogdandrutu]

@shelbyspees per @Aneurysm9 feedback, please consider a separate PR to address that feedback :)