[docs] Simplify troubleshooting doc (open-telemetry#8554)

**Description:** 

Remove bits mentioning configuration on versions v0.42.0 or below and
versions v0.35.0 and below.

These versions are more than 2 years old, and users can always switch to
the docs when their version was released.

docs/troubleshooting.md

@@ -11,8 +11,6 @@ Logs can be helpful in identifying issues. Always start by checking the log
 output and looking for potential issues.
 The verbosity level defaults to `INFO` and can be adjusted.
 
-#### Version 0.36 and above:
-
 Set the log level in the config `service::telemetry::logs`
 
 ```yaml
@@ -22,22 +20,12 @@ service:
       level: "debug"
 ```
 
-#### Version 0.35 and below:
-
-Pass `--log-level` flag to the `otelcol` process. See `--help` for more details.
-
-```console
-$ otelcol --log-level DEBUG
-```
-
 ### Metrics
 
 Prometheus metrics are exposed locally on port `8888` and path `/metrics`. For
 containerized environments it may be desirable to expose this port on a
 public interface instead of just locally.
 
-#### Version 0.43.0 and above:
-
 Set the address in the config `service::telemetry::metrics`
 
 ```yaml
@@ -47,15 +35,6 @@ service:
       address: ":8888"
 ```
 
-#### Version 0.42.0 and below:
-
-Pass `--metrics-addr <ADDR>` flag to the `otelcol` process. See `--help` for
-more details.
-
-```console
-$ otelcol --metrics-addr 0.0.0.0:8888
-```
-
 A Grafana dashboard for these metrics can be found
 [here](https://grafana.com/grafana/dashboards/15983-opentelemetry-collector/).