chore: re-add versioning diagrams (#18713)

RELEASES.md

@@ -7,7 +7,7 @@ The Cosmos-SDK follows both [0ver](https://0ver.org/) and [Semver](https://semve
 Although we adhere to semantic versioning (semver), we have introduced a few modifications to accommodate the unique characteristics of blockchains. One significant divergence is that the major version (Y.x.x) is incremented solely when a consensus-breaking change occurs. On the other hand, the minor version (x.Y.x) is increased when there is a non-consensus-breaking alteration that also results in an incompatible API change. Patch versions will be bumped for all other changes that dont break the API nor Consensus. 
 
 <p align="center">
-  <img src="docs/static/img/semver.png?raw=true" alt="Releases Semver decision tree" width="40%" />
+  <img src="docs/semver.png?raw=true" alt="Releases Semver decision tree" width="40%" />
 </p>
 
 ## 0ver Dependencies
@@ -15,5 +15,5 @@ Although we adhere to semantic versioning (semver), we have introduced a few mod
 In terms of the Cosmos-SDK dependency, we adhere to a simpler versioning approach known as 0ver. This flow differs from the previous Semver flow. Under this system, when a consensus-breaking change or an API-breaking change occurs, the Cosmos-SDK team increments the minor version (x.Y.x). Conversely, when a non-consensus-breaking change and a non-API-breaking change take place, the team bumps the patch version (x.x.Y).
 
 <p align="center">
-  <img src="docs/static/img/0ver.png?raw=true" alt="Releases 0ver decision tree" width="40%" />
+  <img src="docs/0ver.png?raw=true" alt="Releases 0ver decision tree" width="40%" />
 </p>