Covers the same case as open-telemetry#11509

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

Covers the same case as
#11509

#### Description

My previous PR (#11615) which made `component/componenttest` into its
own module tagged it as `v0.113.0` in the requirements of other modules.
This works locally because of the `replace` statements, but since the
module was never _actually_ released as v0.113.0, this causes issues in
contrib (cf. #11509 and #11511).

This PR updates those requirements to use a pseudo-version pointing at a
recent commit on main, which should be properly externally resolvable.

#### Link to tracking issue
None.

#### Testing
I removed the `replace` statements for `componenttest`, ran `make
gotidy`, which allowed `make otelcorecol` to run successfully. Not sure
if this is a thorough enough test however. Once this PR is merged, I
will try `make update-otel [...]` on contrib with the appropriate commit
ID to check that the issue is resolved.

…pendencies (open-telemetry#11509)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

Say we have three modules, A, B, and C, with dependencies C->B->A. If we
are on commit 1, and make a new commit, 2, where we change the
dependencies such that the go.mod files read C@2->B@1->A@1, we will
still get a failure, because at commit 1 we had not yet made the changes
necessary to properly resolve these modules. Specifically, at commit 2
we have B@1->A@#, where A@# is not externally-resolvable.

We therefore need to make a new commit 3, where we can have
C@2->B@2->A@2, and at commit 2 all modules are externally-resolvable.

This PR is a necessary update to
open-telemetry#11503.

When running `make update-otel` in contrib, I am seeing the following
errors:

```
go: downloading go.opentelemetry.io/collector/connector/connectortest v0.0.0-20241021181817-007f06b7c4a8
go: go.opentelemetry.io/collector/pipeline/[email protected]: reading go.opentelemetry.io/collector/pipeline/pipelineprofiles/go.mod at revision pipeline/pipelineprofiles/v0.111.0: unknown revision pipeline/pipelineprofiles/v0.111.0
```

connectortest has an indirect dependency on pipelineprofiles, and at
commit `007f06b7c4a8` pipelineprofiles is versioned at v0.111.0. The
latest commit, `403c782d50c6`, will version it at `007f06b7c4a8`. Since
pipelineprofiles has no dependencies, this will not result in any
issues.

…try#11512)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

Covers the same case as
open-telemetry#11509

…y#11668)

#### Description

My previous PR (open-telemetry#11615) which made `component/componenttest` into its
own module tagged it as `v0.113.0` in the requirements of other modules.
This works locally because of the `replace` statements, but since the
module was never _actually_ released as v0.113.0, this causes issues in
contrib (cf. open-telemetry#11509 and open-telemetry#11511).

This PR updates those requirements to use a pseudo-version pointing at a
recent commit on main, which should be properly externally resolvable.

#### Link to tracking issue
None.

#### Testing
I removed the `replace` statements for `componenttest`, ran `make
gotidy`, which allowed `make otelcorecol` to run successfully. Not sure
if this is a thorough enough test however. Once this PR is merged, I
will try `make update-otel [...]` on contrib with the appropriate commit
ID to check that the issue is resolved.

…pendencies (open-telemetry#11509)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

Say we have three modules, A, B, and C, with dependencies C->B->A. If we
are on commit 1, and make a new commit, 2, where we change the
dependencies such that the go.mod files read C@2->B@1->A@1, we will
still get a failure, because at commit 1 we had not yet made the changes
necessary to properly resolve these modules. Specifically, at commit 2
we have B@1->A@#, where A@# is not externally-resolvable.

We therefore need to make a new commit 3, where we can have
C@2->B@2->A@2, and at commit 2 all modules are externally-resolvable.

This PR is a necessary update to
open-telemetry#11503.

When running `make update-otel` in contrib, I am seeing the following
errors:

```
go: downloading go.opentelemetry.io/collector/connector/connectortest v0.0.0-20241021181817-007f06b7c4a8
go: go.opentelemetry.io/collector/pipeline/[email protected]: reading go.opentelemetry.io/collector/pipeline/pipelineprofiles/go.mod at revision pipeline/pipelineprofiles/v0.111.0: unknown revision pipeline/pipelineprofiles/v0.111.0
```

connectortest has an indirect dependency on pipelineprofiles, and at
commit `007f06b7c4a8` pipelineprofiles is versioned at v0.111.0. The
latest commit, `403c782d50c6`, will version it at `007f06b7c4a8`. Since
pipelineprofiles has no dependencies, this will not result in any
issues.

…try#11512)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

Covers the same case as
open-telemetry#11509

…y#11668)

#### Description

My previous PR (open-telemetry#11615) which made `component/componenttest` into its
own module tagged it as `v0.113.0` in the requirements of other modules.
This works locally because of the `replace` statements, but since the
module was never _actually_ released as v0.113.0, this causes issues in
contrib (cf. open-telemetry#11509 and open-telemetry#11511).

This PR updates those requirements to use a pseudo-version pointing at a
recent commit on main, which should be properly externally resolvable.

#### Link to tracking issue
None.

#### Testing
I removed the `replace` statements for `componenttest`, ran `make
gotidy`, which allowed `make otelcorecol` to run successfully. Not sure
if this is a thorough enough test however. Once this PR is merged, I
will try `make update-otel [...]` on contrib with the appropriate commit
ID to check that the issue is resolved.