Update Java and .NET version comments (#4532)

- Update comments to avoid people trying to update values that appear wrong.
- Fix broken warning in RELEASE.md.

See #4530.

Author: martincostello

RELEASE.md

@@ -8,7 +8,8 @@ Steps to release a new version of the OpenTelemetry Operator:
       - Operator, target allocator and opamp-bridge should be `$VERSION`.
       - OpenTelemetry Collector should be the latest collector version. The `major.minor` should typically match, with the patch portion being possibly different.
       - The `autoinstrumentation-*` versions should match the latest supported versions in `autoinstrumentation/`.
-        > [!WARNING]
+        > **:warning: Warning**
+        >
         > DO NOT BUMP JAVA PAST `1.X.X` AND DO NOT BUMP .NET PAST `1.2.0`. Upgrades past these versions will introduce breaking HTTP semantic convention changes.
    1. Check if the compatible OpenShift versions are updated in the `Makefile`.
    1. Update the bundle by running `make bundle reset VERSION=$VERSION`.

versions.txt

@@ -14,7 +14,7 @@ targetallocator=0.140.0
 operator-opamp-bridge=0.140.0
 
 # Represents the current release of Java instrumentation.
-# Should match autoinstrumentation/java/version.txt
+# This version should not be greater than 1.x.x.
 autoinstrumentation-java=1.33.6
 
 # Represents the current release of NodeJS instrumentation.
@@ -26,7 +26,7 @@ autoinstrumentation-nodejs=0.66.0
 autoinstrumentation-python=0.59b0
 
 # Represents the current release of DotNet instrumentation.
-# Should match autoinstrumentation/dotnet/version.txt
+# This version should remain pinned to 1.2.0.
 autoinstrumentation-dotnet=1.2.0
 
 # Represents the current release of Go instrumentation.