[chore] Fix make for-all command (open-telemetry#43572)

#### Description

open-telemetry#43509 changed the `make for-all` Makefile target to access the
`ALL_MODS` variable through environment variables instead of expanding
it into the shell command, in order to bypass Windows' 8192 byte command
line length limit.

However, the environment variable was not defined, which led to `make
for-all` becoming a no-op. This can be confirmed by running `make
for-all CMD='echo test'`.

(I discovered this issue because [this
PR](open-telemetry/opentelemetry-collector#13996)
in core repository, which should be failing `contrib-tests`, suddenly
started passing them. This was because the job inserts `replace`
statements in a copy of contrib using `for-all`; failing to do that
caused the contrib tests to run against whatever version of core is
imported here rather than against the PR's code.)

This PR fixes that oversight, by adding the `export` keyword to the
`ALL_MODS` variable.

Author: jade-guiton-dd

Makefile

@@ -45,7 +45,7 @@ PKG_MODS := $(shell find ./pkg/* $(FIND_MOD_ARGS) -exec $(TO_MOD_DIR) )
 CMD_MODS_0 := $(shell find ./cmd/[a-z]* $(FIND_MOD_ARGS) -not -path "./cmd/otel*col/*" -exec $(TO_MOD_DIR) )
 CMD_MODS := $(CMD_MODS_0)
 OTHER_MODS := $(shell find . $(EX_COMPONENTS) $(EX_INTERNAL) $(EX_PKG) $(EX_CMD) $(FIND_MOD_ARGS) -exec $(TO_MOD_DIR) )
-ALL_MODS := $(RECEIVER_MODS) $(PROCESSOR_MODS) $(EXPORTER_MODS) $(EXTENSION_MODS) $(CONNECTOR_MODS) $(INTERNAL_MODS) $(PKG_MODS) $(CMD_MODS) $(OTHER_MODS)
+export ALL_MODS := $(RECEIVER_MODS) $(PROCESSOR_MODS) $(EXPORTER_MODS) $(EXTENSION_MODS) $(CONNECTOR_MODS) $(INTERNAL_MODS) $(PKG_MODS) $(CMD_MODS) $(OTHER_MODS)
 
 CGO_MODS := ./receiver/hostmetricsreceiver
 
@@ -222,7 +222,7 @@ goporto: $(PORTO)
 
 .PHONY: for-all
 for-all:
-	@set -e; for dir in $${ALL_MODS}; do \
+	@set -e; for dir in $$ALL_MODS; do \
 	  (cd "$${dir}" && \
 	  	echo "running $${CMD} in $${dir}" && \
 	 	$${CMD} ); \

receiver/ciscoosreceiver/documentation.md

@@ -18,7 +18,7 @@ Number of bytes received on the interface
 
 | Unit | Metric Type | Value Type |
 | ---- | ----------- | ---------- |
-| bytes | Gauge | Int |
+| By | Gauge | Int |
 
 #### Attributes
 
@@ -33,7 +33,7 @@ Number of receive errors on the interface
 
 | Unit | Metric Type | Value Type |
 | ---- | ----------- | ---------- |
-| errors | Gauge | Int |
+| {error} | Gauge | Int |
 
 #### Attributes
 
@@ -48,7 +48,7 @@ Number of bytes transmitted on the interface
 
 | Unit | Metric Type | Value Type |
 | ---- | ----------- | ---------- |
-| bytes | Gauge | Int |
+| By | Gauge | Int |
 
 #### Attributes
 
@@ -63,7 +63,7 @@ Number of transmit errors on the interface
 
 | Unit | Metric Type | Value Type |
 | ---- | ----------- | ---------- |
-| errors | Gauge | Int |
+| {error} | Gauge | Int |
 
 #### Attributes
 
@@ -89,19 +89,19 @@ Interface operational status (1 for up, 0 for down)
 
 ### cisco.system.cpu.utilization
 
-CPU utilization percentage
+CPU utilization as a fraction
 
 | Unit | Metric Type | Value Type |
 | ---- | ----------- | ---------- |
-| % | Gauge | Double |
+| 1 | Gauge | Double |
 
 ### cisco.system.memory.utilization
 
-Memory utilization percentage
+Memory utilization as a fraction
 
 | Unit | Metric Type | Value Type |
 | ---- | ----------- | ---------- |
-| % | Gauge | Double |
+| 1 | Gauge | Double |
 
 ## Resource Attributes