fix(semconv): update database semantic conventions link for blog posts

Signed-off-by: Vitor Vasconcellos <[email protected]>

Author: vitorvasc

content/en/blog/2024/spring-starter-stable/index.md

@@ -79,7 +79,7 @@ Note that the Spring Starter uses some semantic conventions that are not stable,
 which are still evolving and may change in the future.
 [HTTP semantic conventions](/docs/specs/semconv/http/http-metrics/) are stable
 and will not change.
-[Database semantic conventions](/docs/specs/semconv/database/database-metrics/)
+[Database semantic conventions](https://github.com/open-telemetry/semantic-conventions/blob/v1.38.0/docs/database/database-metrics.md)
 are still experimental and may change. However, they are expected to become
 stable at the end of 2024.
 

content/en/blog/2025/complex-attribute-types.md

@@ -71,7 +71,7 @@ Examples include:
   inherently structured
 - **GraphQL** — responses may include
   [lists of structured errors](https://graphql.org/learn/response/#errors)
-- **[Database operations](/docs/specs/semconv/database/database-spans)** — batch
+- **[Database operations](https://github.com/open-telemetry/semantic-conventions/blob/v1.38.0/docs/database/database-metrics.md)** — batch
   operations have properties that flat attributes cannot adequately capture
 
 Before extending support for complex attributes to all signals, we explored

content/en/docs/languages/python/propagation.md

@@ -125,7 +125,7 @@ This supports context propagation between database client and server when
 database log records are enabled. For more information, see:
 
 - [OpenTelemetry Python sqlcommenter example](https://github.com/open-telemetry/opentelemetry-python/tree/main/docs/examples/sqlcommenter/)
-- [Semantic Conventions - Database Spans](/docs/specs/semconv/database/database-spans/#sql-commenter)
+- [Semantic Conventions - Database Spans](/docs/specs/semconv/db/database-spans/#sql-commenter)
 - [sqlcommenter](https://google.github.io/sqlcommenter/)
 
 ## Next steps