Use GMF Warning/Caution (#5220)

docs/trace/reporting-exceptions/README.md

@@ -142,7 +142,7 @@ It might be useful to automatically capture the unhandled exceptions, travel
 through the unfinished activities and export them for troubleshooting. Here goes
 one possible way of doing this:
 
-> **Warning**
+> [!CAUTION]
 > Use `AppDomain.UnhandledException` with caution. A throw in the
 handler puts the process into an unrecoverable state.
 

src/OpenTelemetry.Instrumentation.GrpcNetClient/README.md

@@ -7,7 +7,7 @@ This is an [Instrumentation Library](https://github.com/open-telemetry/opentelem
 which instruments [Grpc.Net.Client](https://www.nuget.org/packages/Grpc.Net.Client)
 and collects traces about outgoing gRPC requests.
 
-> [!NOTE]
+> [!CAUTION]
 > This component is based on the OpenTelemetry semantic conventions for
 [traces](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/rpc/rpc-spans.md).
 These conventions are

src/OpenTelemetry.Instrumentation.SqlClient/README.md

@@ -11,12 +11,12 @@ and
 [System.Data.SqlClient](https://www.nuget.org/packages/System.Data.SqlClient)
 and collects traces about database operations.
 
-> **Warning**
+> [!WARNING]
 > Instrumentation is not working with `Microsoft.Data.SqlClient` v3.* due to
 the [issue](https://github.com/dotnet/SqlClient/pull/1258). It was fixed in 4.0
 and later.
->
-> [!NOTE]
+<!-- This comment is to make sure the two notes above and below are not merged -->
+> [!CAUTION]
 > This component is based on the OpenTelemetry semantic conventions for
 [traces](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md).
 These conventions are